As a first step, check your connectivity to the Mastercard Payment Gateway.
Before you start building the integration, you must be prepared with the values for the fields that require your input.
Creating the body of the request is a critical step in the integration.
There are many components to making sure the transaction request is sent securely to the Mastercard Payment Gateway.
Once a transaction request has been sent to the gateway, you will generally receive a response within a very short period. You will need to process this in order to complete the transaction.
Testing allows you to check if your integration is working as desired.
Go to the appropriate (REST/NVP) [all versions] link in the Protocol Documentation section on the API Reference index page.
Yes, the API field names for all operations are case-sensitive.
If using HTTP POST, include the request parameters in the HTTP body using JSON encoding. With HTTP GET, ensure the request parameters are included in the URI as query parameters.
Merchant-defined fields are not supported in this version of the Mastercard Payment GatewayAPI.
The re-submitted identical transaction will return the same response as the first. All operations in this version of the Mastercard Payment GatewayAPI are idempotent; that is, the effects of repeated identical requests are the same as that for a single request. Therefore you can be assured that the transaction will not be repeated with your or the payer's bank.
From API v15 onwards, if the initial transaction for an order fails, you can submit a new initial transaction (with a new transaction ID) for this order without having to create a new order.
From API v15 onwards, if you want to perform a subsequent Capture or a Refund transaction against a successful initial transaction, you must NOT provide card details in your request. If you provide card details when the order already has a successful initial transaction, then the Mastercard Payment Gateway rejects the request.
When you do not receive a response, it is recommended that you wait for 60 seconds and attempt to resubmit the identical request. The bank transaction will not be repeated again and rest assured no duplicate funds will be transferred. You will receive the same response as you would have received for the first request.
All approved transactions are represented with a Transaction Response Code of APPROVED
from the Mastercard Payment Gateway. Any other code represents a declined or failed transaction.
The re-submitted identical transaction will return the same response as the first as all operations in the Mastercard Payment Gateway are idempotent (the side-effects of N > 0 identical requests is the same as for a single request). So, you can be assured that the transaction will not be repeated with your or the payer's bank.
It is highly recommended that you validate the SSL certificate of the Mastercard Payment Gateway whenever you connect to the Mastercard Payment Gateway. the Mastercard Payment Gateway SSL certificate is issued by an industry standard Certificate Authority such as Verisign or Thawte whose root certificate should already be available in your web environment.