Create a Card Transaction
This section provides a high-level view of the available card transaction models.
For implementation details, complete request and response examples, and model-specific behavior, refer to:
- Raw Card Payment available for credit card and debit card.
- Token Credit Card Payment only for credit card.
Available models
The API supports two card integration models:
- Explicit model: the merchant explicitly informs whether the transaction should be processed as
CREDIT_CARDorDEBIT_CARD - Flexible model: the merchant sends the card as
CARD, and the issuer-defined method used in authorization is returned in the response
Availability matrix
| Capability | Explicit model | Flexible model | Tokenized card |
|---|---|---|---|
| Credit card support | Yes | Yes | Yes |
| Debit card support | Yes | Yes | No |
| Merchant explicitly informs card method | Yes | No | Yes |
| Issuer-defined card method returned in response | Yes | Yes | No |
| Available in raw integration | Yes | Yes | No |
| Available in tokenization flow | No | No | Yes |
Important note
Debit card processing is currently available only through the raw card integration flow.
For the tokenized card flow, only credit card is currently available. Debit card is not supported in tokenization.
If you need to process debit card transactions, use the raw integration described in:
When to use each model
Explicit model
Use this model when your checkout already separates credit and debit flows and you want the API to validate the expected method against the type reported by the issuing bank.
Flexible model
Use this model when you want a simpler card integration and prefer the issuer-reported card method to define whether the transaction is processed as credit or debit.
Next step
Go to Raw Card Payment for the full implementation guide, including request structure, response structure, examples, and error handling.
Or go to - Token Credit Card Payment for Credit Card.
Updated about 6 hours ago
