- Integration Guidelines
- Implementing a Merchant Boarding API Integration
- Update Merchant Payment Details
Update Merchant Payment Details
Allows you to add or update payment configuration details for an existing merchant. The payment details include details about how a merchant will transact (Authorize, Pay or both), the supported transactions (for example, Verification Only, Refund, Standalone Capture transactions) and the associated privileges. It also allows you to enable/disable and configure services offered by the Suncorp Bank Gateway such as API, Reporting, Hosted Payment Form, Batch Integration, Tokenization, Transaction Filtering and Risk Management.
Enabling or Disabling Gateway Tokenization
Gateway Tokenization allows merchants to store payment details in a secured environment in exchange for a token. This is useful to merchants as they do not have to comply with all of the restrictions and regulations associated with storing sensitive payment data on their system and it reduces their PCI-compliance obligations. The token can be used in place of payment details in transaction requests to the gateway. Further, if the payment details are stored into a token as part of a customer registration or account creation process, the token may be used when the payer returns to make another purchase.
You can enable Gateway Tokenization by providing a token repository ID in the Update Merchant Payment Details request. If you want to disable Tokenization after enabling it, exclude the token repository ID from the request. For more details, see Gateway Tokenization Information.
Enabling or Disabling Network Tokenization
Network tokenization, also known as Scheme Tokenization, allows merchants to securely replace the payer's primary Account Number (PAN) with a network token generated by network tokenization service providers such as Mastercard Digital Enablement Service (MDES). You, on behalf of your merchant can request for both new and existing account PANs on file to be tokenized and each PAN to be replaced with a unique network token (subject to issuer participation in the network tokenization service and the enabled card account ranges). The Authorization/Pay request initiated by merchants will attempt to use the network token if available, else the Funding PAN (FPAN) stored against the gateway token will be used.
To use Network Tokenization, you must be first enabled for Gateway Tokenization.
You can enable network tokenization for a scheme by providing fields specific to the network tokenization provider in the Update Merchant Payment Details or Create or Update request. To disable it after enabling it, exclude these fields from the request. For more details, see Network Tokenization Information.
Enabling or Disabling Transaction Filtering
Transaction Filtering enables the gateway to reject or mark transactions for review based on simple rules. You can configure rules per merchant and/or rules that apply to all merchants (via Merchant Manager). Merchants can configure rules themselves via Merchant Administration. If any individual rule fails, the gateway will reject the transaction or mark it for review and the order will not be allowed to proceed. See Transaction Filtering Rules Information for details on how to use Update Merchant Payment Details to configure rules for a merchant.
Enabling or Disabling External Risk Providers
You can enable an external risk provider for a merchant to risk assess their transactions performed through the gateway.
The gateway currently supports the following risk providers: Accertify Interceptas, GateKeeper, NuDetect. For more information, see Risk Management.
Enabling or Disabling Dynamic Currency Conversion (DCC)
DCC services enable merchants to accept payments in the currencies of their order from payers whose currencies are different. See Enabling Dynamic Currency Conversion for how to enable DCC.
If you want to disable DCC after enabling it, exclude all DCC-related fields from a request.
Enabling or Disabling Masterpass
Masterpass is a digital wallet provider that allows payers to store their payment details such as card details, billing and shipping address in a secure server. When paying online the payer can simply log onto Masterpass and select the stored payment details, saving the payer from having to provide their payment details every time they pay online.
You can enable Masterpass for your merchant by providing an checkout identifier in the Update Merchant Payment Details request. If you want to disable Masterpass after enabling it, exclude the checkout identifier from the request. See Masterpass Information for details on how to use Update Merchant Payment Details to configure Masterpass.