Enable your customers with recurring payment
As the payment system has evolved, instances in which a transaction is initiated with a stored credential based on a shopper’s consent for future use have increased to significant levels.
Growth in digital commerce, together with the emergence of new business models, has increased the number of transactions where merchants use shoppers’ payment credentials (i.e., account details) that they previously stored for future purchases. Recognizing stored credential transactions distinctly allows for:
- Results in higher authorization approval rates and completed sales
- Fewer customer complaints and improved checkout experience
- Greater visibility of transaction risk levels
This document defines authorization data values Airwallex uses to identify initial storage and usage of stored payment credentials to enable recurring payment processing. A new domain
PaymentConsent is added to Payment Acceptance to hold details required for recurring payments and references to PaymentMethod and Customer. A
PaymentConsent represents the consent between merchant and shopper that how the shopper's credentials will be used for subsequent transactions. You may create and add multiple
PaymentConsents to a Customer. A
PaymentConsent needs to be created and verified with a valid
PaymentMethod can be used for multiple payment consents.
Merchant initiated transactions (MIT)
In this type of transaction, the shopper allows the merchant to initiate the transactions at an agreed amount using the shopper's selected payment method during the agreed time frame.
- For the first transaction, the shopper provides merchant consent to store their payment details for future payments at agreed amount and timeframe.
- In subsequent transactions, the shopper will not be present in the payment. The merchant initiates transactions as agreed with the shopper.
Customer initiated transactions (CIT)
In this type of transaction, the shopper needs to be present for subsequent transactions without the need to input payment details.
- For the first transaction, the shopper provides merchant consent to store their payment details for future payments.
- In subsequent transactions, the shopper will not need to input payment details and can simply make payment by one click. The merchant has the flexibility to request the shopper to provide/not provide CVC/CVV in the subsequent transactions.
|Integration Type||Supported||Required PCI-DSS||Notes|
|HPP (Hosted Payment Pages)||✅||PCI-DSS SAQ||Self-service questionnaire, all Merchants can do it|
|Embedded fields||✅||PCI-DSS SAQ||Self-service questionnaire, requires additional knowledge|
|Drop-in elements||✅||PCI-DSS SAQ||Self-service questionnaire, requires additional knowledge|
|API||✅||PCI-DSS AOC||AOC by 3rd party required|