Process an online transaction where the card is not physically present.
With the Transactions API, you can initiate an e-commerce transaction (entryType Ecom) using:
- Card: Card-not-present payments with PAN, expiry, and optional CVC.
- Token: Payments using a scheme token or a stored gateway token.
- Apple Pay: Wallet payments using an Apple Pay token decrypted on your backend.
- Google Pay: Wallet payments using a Google Pay token decrypted on your backend.
- SPEI: Pay-by-bank deposits and payouts in Mexico (
MXN). - CVU: Pay-by-bank deposits and payouts in Argentina (
ARS). Deposits use a provisioned CVU account and payouts use a create-transaction call. - Bre-B: Pay-by-bank deposits and payouts in Colombia (
COP). Deposits use a provisioned Bre-B Llave and payouts use a create-transaction call.
Which methods you can use depends on your merchant and site configuration.
The following optional features can be combined with supported e-commerce payment methods where enabled for your site.
| Feature | Description |
|---|---|
| Recurring payments | Charge a stored card on a recurring basis using card-on-file or merchant-initiated processing models. |
| 3D Secure and PSD2 | Add 3D Secure authentication data or PSD2 SCA exemptions to card and wallet transactions. Required for many European online payments. |
| AVS and IDV | Verify that the billing address (AVS) or cardholder name (IDV) matches the issuer's records. |
| Dynamic descriptors | Set the description that appears on the cardholder's statement so they can recognise the charge. |
| Shopper details | Include shopper contact and address details on the transaction request. |
| DCC rate | Pass Dynamic Currency Conversion rate and amount data when the cardholder pays in their home currency. |