The hosted checkout integration supports two types of transactions:
-
Customer-initiated transactions: This type of transaction is initiated by the customer and the customer is actively participating in the transaction. For example, your customer places an order and completes the transaction through your integration or provides a payment card to be saved to their profile.
-
Merchant-initiated transactions: This type of transaction is initiated by the merchant and the customer is not actively participating in the transaction. Your customer previously authorized you to use their payment card for a future transaction. For example, you offer a wine club subscription and you charge your guests monthly for the subscription.
A customer-initiated transaction must be completed before you can
complete a merchant-initiated transaction. The customer-initiated
transaction can be completing and confirming payment intent or setting up
and saving a payment card for future use. The customer-initiated
transaction creates a mandateId and stores the payment card
as a card-on-file. A
card-on-file is a payment card that your customer explicitly authorizes
your integration to securely store and use for the agreed upon future
transaction(s).
During the customer-initiated transaction workflow, your customer can choose to save and store their card-on-file as a saved card. A saved card is a payment method that is attached to a customer record. The saved card can be used to authorize and complete merchant-initiated transactions.
|
Note |
|
The customer must be logged into your integration to select their
saved cards in the hosted checkout |