Save payment details for future payments
The growth in payments technology for digital commerce together with the emergence of new business models, has seen a significant rise in payments that use shopper’s saved payment details. The payment is initiated based on the shopper’s consent to use the saved payment details for future use. Identifying the initial consent for saving payment details and the use of saved payment details for subsequent payments can:
- Result in higher authorization approval rates and completed sales
- Fewer shopper complaints and improved checkout experience
- Greater visibility of transaction risk levels
Airwallex allows you to create a PaymentConsent API that represents the consent between you and the shopper on the future use of the saved payments details associated with a Customer API.
- You can create and add multiple PaymentConsents to a Customer.
- A PaymentConsent requires a valid PaymentMethod API.
- A PaymentMethod can be used for multiple PaymentConsents.
Merchant-initiated subsequent payments
Merchant-initiated subsequent payments, also known as Merchant Initiated Transactions (MIT), alllow you to initiate payments at an agreed amount using the shopper's selected payment method during the agreed time frame.
- In the initial interaction (with or without payment), the shopper provides consent to store their payment details for future payments for an agreed amount and timeframe.
- In subsequent payments, you initiate payments as agreed with the shopper without the shopper involved.
Customer-initiated subsequent payments
Customer-initiated subsequent payments, also known as Customer Initiated Transactions (CIT), require the shopper to be present without the need to enter payment details.
- In the initial interaction (with or without payment), the shopper provides consent to store their payment details for future payments.
- In subsequent payments, the shopper will not be required to enter payment details and can simply make payments by one click. You can choose to request the shopper to provide CVC in the subsequent payment.
Integration options
| Integration Type | Supported | Required PCI-DSS | Notes |
|---|---|---|---|
| Hosted Payment Page | ✅ | PCI-DSS SAQ | Self-service questionnaire, all Merchants can do it |
| Embedded Elements | ✅ | PCI-DSS SAQ | Self-service questionnaire, requires additional knowledge |
| Drop-in Element | ✅ | PCI-DSS SAQ | Self-service questionnaire, requires additional knowledge |
| Native API | ✅ | PCI-DSS AOC | AOC by 3rd party required |
See also Redirect/QR Code Element.