EC API Global

Card Transaction Flow

The card transaction flow enables customers to make secure payments using their credit or debit cards, providing a convenient and widely accepted method for transactions. The two different types of card transaction flow are:

  1. New Card Transaction Flow: This flow allows customers to enter their card details during checkout for processing a payment. It is suitable for first-time users or customers who prefer to provide card information manually.

    For integration enablement,

    1. Call “Card Info” APIlink icon - Get Card details using card bin. You can also use this API to check if a card is eligible for Mandate or direct OTP payments.

    2. Call “Card transaction” API link icon- Call this API using Card details and cvv provided by the customer to initiate a card transaction

  2. Saved Card Transaction Flow: With this flow, customers can conveniently complete transactions using their previously saved card details. It offers a streamlined checkout experience for returning customers, eliminating the need to re-enter card information.

    For integration enablement,

    1. Call “List Card” APIlink icon - List all the cards stored for a customer. This API gives back only card tokens and other metadata relevant to the cards stored against the customer.

    2. Call “Card transaction” APIlink icon - Call this API using card token and cvv provided by the customer to initiate a card transaction

Both flows prioritize security and aim to provide a seamless payment experience for customers using card-based payments.

Integration Architecture

Image 1
Warning

  • Compliance Check: Merchants who are not PCI DSS compliant should refrain from using this API and consume our PayV3.jslink icon for cards.

Modes Of Card Transaction

Based on the authentication process in card transactions, liability for authentication can fall on the merchant or card issuer. The following modes of transactions are defined accordingly:

  1. 3DS Card Transaction
    Involves user authentication through an OTP or similar method, ensuring liability shifts to the card issuer. Refer 3DS Card Transactionlink icon for description and integration steps.

  2. 3DS-Frictionless Card Transaction
    Skips OTP authentication for low-risk transactions, with liability remaining with the card issuer after risk assessment. Refer 3DS-Frictionless Card Transactionlink icon for description and integration steps.

  3. No-3DS Card Transaction
    Skips authentication entirely, typically for specific low-risk scenarios, with liability falling on the merchant. Refer No-3DS Card Transactionlink icon for description and integration steps.

  4. Pre-auth and Capture Card Transaction
    Authorizes a specific amount initially and captures the amount later, allowing flexibility for merchants in managing payments. Refer Pre-auth and Capture Card Transactionlink icon for description and integration steps.

Gateway Supported List:

Scroll inside to view more
Gateway
3DS
3DS-FRICTIONLESS
N0-3DS
Pre-Auth and Capture
2C2P
Yes
Yes
Midtrans
Yes
Yes
Yes
Dlocal
Yes
Yes
Yes
Stripe
Yes
Yes
Yes
Yes
Payfort
Yes
Yes
Yes
Yes
Checkout
Yes
Yes
Yes
Yes
Worldpay
Yes
Yes
Yes
Yes
HyperPG (Juspay)
Yes
Yes
Yes
Yes
Adyen
Yes
Yes
Yes
Yes
Airwallex
Yes
Yes
Yes
Tap Payments
Yes
Yes
Yes
Paymob
Yes
Yes
MyFatoorah
Yes
HyperPay
Yes
Yes
Flutterwave
Yes
Yes
Zaincash
Yes
FastPay
Yes
MPGS
Yes
Yes
Yes
Cybersource
Yes
Yes
Yes
Last updated 1 year ago