General information

Payment card verification is a process that ensures the validity of the payer's card, confirms its absence in blacklists, and establishes the likelihood of its use by the rightful owner (cardholder) even before the primary financial transaction is initiated.

Features:

• Payment card verification operations have the "Lookup" type and are displayed with this value in the merchant portal.
• Utilizing the feature enables you to generate a payment card token, which can be subsequently employed for recurring payments.

caution

Note: primary payments (purchase, auth, credit, lookup, P2P) must have a unique order ID. In case the selected order ID is already set for another transaction, an error will be received when creating the order.

The following options are available for card verification:

• Verification with a pre-authorization when funds are held in the customer’s bank account and completion of 3DS verification.
• Verification involving the debit of funds from the customer's bank account and completion of 3DS verification.
• Non-debit card verification, with confirmation through the entry of a lookup code.
• Non-debit card verification without the need for transaction confirmation.

Verification with a pre-authorization when funds are held in the customer's bank account and completion of 3DS verification

This verification method is executed without charging the customer's bank account. The transaction is confirmed by the customer either through their mobile application or by entering a one-time password (OTP), provided the payment card supports 3DS verification.

Interaction format:

1. The customer inputs card details on the checkout page.
2. Confirmation is completed through the customer's bank mobile app or by entering a one-time password (OTP).
3. A pre-authorization (hold) of UAH 1 is made on the customer's account.
4. You obtain verification result:
   • Successful verification returns a card token for its use in direct API integration or recurring payments.
   • Failed verification means no card token is generated. This result may signal input errors, fraudulent attempts, insufficient funds, or unconfirmed operations, requiring additional attention.
5. After a successful check, you should initiate a void transaction with respect to the pre-authorization. Otherwise, the pre-authorized amount will be released automatically within a period of 7 to 30 days, depending on the issuing bank.

Verification involving the debit of funds from the customer's bank account and completion of 3DS verification.

This verification method involves debiting funds from the customer's bank account, with confirmation from the customer through their mobile application or by entering a one-time password (OTP), provided that the payment card supports 3DS verification.

Interaction format:

1. The customer inputs card data on the checkout page.
2. The customer confirms the operation through the mobile application of their bank or by entering a one-time password (OTP).
3. Funds in the amount of UAH 1 are debited from the customer's account (purchase transaction is made).
4. You receive the result of the verification check:
   • Successful verification returns a card token, usable for transactions through direct API integration or recurring payments.
   • Failed verification means no card token is generated. This result may signal errors in entering card data/OTP or a potential fraud attempt, requiring your additional attention. It could also result from insufficient funds in the customer's bank account or the customer not confirming the operation.
5. After successful verification, it is essential to initiate the refund operation.

caution

A delayed refund of funds to the customer may lead to disputes regarding the corresponding payment (chargeback).

Non-debit card verification, with confirmation through the entry of a lookup code

This verification method is conducted without debiting or holding funds on the customer's bank account (pre-authorization), allowing it to proceed irrespective of the available balance. However, it necessitates confirmation through the mobile application or by entering a one-time password (lookup code).

Interaction format:

1. The customer inputs card data on the checkout page.
2. We transmit the lookup code to the issuing bank (via the acquiring bank) to validate the transaction.
3. The issuing bank dispatches the lookup code to the customer through a push message in the mobile application or via SMS.
4. The customer confirms the operation using the bank's mobile application or by entering the lookup code in the form displayed after clicking the action button on the checkout page.
5. You receive the verification result:
   • Successful verification returns a card token, enabling transactions through direct API integration or recurring payments.
   • Failed verification means no card token is generated. The outcome may signal errors in entering card data/lookup code or a potential fraud attempt, requiring your additional attention. This result may also occur if the customer fails to confirm the operation or enters an incorrect lookup code.

Non-debit card verification without the need for transaction confirmation

This method of verification operates without debiting or holding funds on the customer's bank account (pre-authorization), making it independent of the available balance. Moreover, it doesn't require confirmation from the customer.

Interaction format:

1. The customer inputs card data on the checkout page.
2. We transmit the lookup code to the issuing bank (via the acquiring bank) to validate the transaction.
3. The acquiring bank notifies us on the results of card validation (regardless of the lookup code entry results).
4. You receive the verification result:
   • Successful verification returns a card token, enabling transactions through direct API integration or recurring payments.
   • Failed verification means no card token is generated. The outcome may indicate errors in entering card data or a potential fraud attempt, requiring your attention.

caution

Failure to confirm the operation in the bank's mobile application or entering an incorrect lookup code does not impact the verification result. Additionally, this method does not serve as confirmation that the card belongs to a specific person (card owner / cardholder).

For information on the suitability of specific card verification methods for your live project, please contact the Tranzzo Support Service.

Verification of payment cards

API integration

Direct interaction of your software with our API at the backend level to exchange data and use our features.