Services

When 3D secure is enabled for all card types; by default 3D authentication will take place for card transaction in all countries. We can enable 3D secure per payment product in our system. You can control the use of 3D secure per transaction through the ‘skipAuthentication’ Boolean in the API. By setting this value to true you can skip the 3D secure checks per transaction based on your own business logic.

Credit/debit cards, direct debit, and PayPal (for certain verticals only) support delayed settlement.

Based on your PCI compliancy status you can use either Create Token or you can use Create Token from the payment API call to save card details on our servers and obtain a token. You can use this token to charge the card at a later date.

Sending a dynamic descriptor does not guarantee that it will appear on the bank statement. It is entirely up to the issuing bank to decide what to show on the statement. Also the authorisation records on an electronic statement can show a different description from the final settled records. Best advice is to limit the full text to 25 characters to prevent unwanted truncation.
For more information on descriptors, click here.

Tokenization is a process of replacing sensitive data with a reference to the data, without compromising security. By referring to tokenized data, you can re-use previously submitted sensitive data without storing this data in your own systems. We issue the token and bear the responsibility for keeping cardholder data safe. Tokenization provides the implementation backbone for one-click payments and recurring payments.

Tokenization can currently be applied to the following payment products:

• Credit/Debit Cards
• Direct Debit (to also store a SEPA Mandate)
• PayPal (to store a billing agreement)

The REST API will tokenize any first of a recurring transaction done with a card that can be tokenized automatically.

For more information about tokenization click here.

Issuers may send a decline response to an authorisation request for an recurring transaction (RT) if that authorisation request has a missing, invalid or incorrect expiry date. This change will enable issuers to include the expiry date in their authorisation decision-making process for recurring transactions. Acquirers and their merchants who use recurring transactions will, therefore be required to supply the correct expiry date in recurring transactions requests.
You can use Create Token/Create Token from the payment and update token API calls to create and update the details of existing card token. The only way to update the data stored in a token you will need to use the update token call.