Credit Card
π³ Credit Card Payments
βΉοΈ For full request and response examples, refer to the API Reference.
To fully leverage our credit card capabilities, itβs essential to understand the key concepts in the transaction lifecycle β from authentication to settlement, refund, and dispute management.
π Key Concepts
Concept | Description |
---|---|
π Authentication (3DS) | 3D Secure (3DS) is a protocol used to authenticate the cardholder before authorization. Based on the issuer's response, the flow can be frictionless or require a challenge. If authentication is successful, the chargeback liability shifts from merchant to issuer. |
π‘οΈ Antifraud (AF) | Antifraud systems analyze transactions based on behavioral, device, and historical risk signals. They may approve, reject, or flag a transaction for manual review before it reaches authorization. |
π¦ Authorization | This is when the transaction is sent to the card issuer and scheme (e.g., Visa, Mastercard) for approval. A pre-authorization reserves funds but does not complete the charge until capture. |
β Cancellation | Cancels an authorized or captured transaction, often due to unfulfilled orders or user action. |
πΈ Refunded | Indicates a full or partial return of funds to the customer after the payment has been captured. |
β οΈ Chargeback Requested | The cardholder has disputed the transaction. Funds are temporarily withdrawn from the merchant while the issuer investigates. |
β Chargeback Refunded | The dispute was accepted by the issuer. The transaction is finalized with a full reversal of funds to the cardholder. |
π·οΈ Accepted Card Brands
Card Brand | One-Time Payment | Installments (Store) | International Support |
---|---|---|---|
Visa | β Yes | β Yes | β Yes |
MasterCard | β Yes | β Yes | β Yes |
American Express | β Yes | β Yes | β Yes |
Elo | β Yes | β Yes | β Yes |
Diners Club | β Yes | β No | β Yes |
Discover | β Yes | β No | β Yes |
JCB | β No | β No | β No |
Aura | β Yes | β Yes | β Yes |
π Credit Card Transaction Flow
sequenceDiagram participant Buyer as π§ Buyer participant Merchant as π Merchant Platform participant A55API as π§© a55 API participant AF as π‘οΈ Antifraud Engine participant ThreeDS as π 3DS Server participant Acquirer as π¦ Acquirer / Provider Buyer->>Merchant: 1. Selects credit card as payment method Merchant->>A55API: 2. Sends transaction request (card + payer data) A55API->>AF: 3. Triggers antifraud analysis AF-->>A55API: Risk decision (approve / reject / review) A55API->>ThreeDS: 4. Initiates 3DS authentication (if enabled) ThreeDS-->>A55API: 5. 3DS result (frictionless / challenge / success / fail) A55API->>Acquirer: 6. Sends transaction for authorization Acquirer-->>A55API: 7. Returns authorization status A55API-->>Merchant: 8. Returns final result
Updated 1 day ago