COF
It is only applicable to EC Scenario.
Consumers save the card information or credentials on the merchant side for subsequent quick payment without having to re-enter the cardNumber, expiryDate, holderName, etc.
Initial Transactions
Merchants help consumers complete the storage of card information (the card information mentioned here does not include cvc) in the following ways:
If you have submitted and completed PCI DSS Self-Assessment Questionnaire D (SAQ D), then you stores the card information locally in the following ways:
- ASI. See chapter Account Status Inquiry (ASI) for more details.
- Small amount transaction Payment (captureAfterHours is not 0) and Cancel. See chapter Payment and chapter Cancel for more details.
- A successful Payment transaction. See chapter Payment for more details.
- The merchant first stores the card information locally, then initiates a transaction, and successfully verifies the validity of the card through the transaction. Note here that when initiating a transaction, it is necessary to increase the collection of cvc to improve the transaction success rate.
From your server, you can make an HTTP POST request to EVO Cloud endpoint
_/g2/v1/payment/mer/{sid}/payment _
and specify the additional parameters below.
| Parameter | Required | Description |
|---|---|---|
paymentMethod.recurringProcessingModel | O | This indicates whether a transaction is a Credential on File (COF) or a recurring transaction. COF: The consumer initiates a payment, and the merchant prompts the consumer to store the credential on file for future cardholder-initiated purchases. |
TIP
If you're only required to submit PCI DSS Self-Assessment Questionnaire A (SAQ A), then you can use Gateway tokenization. You can use payment with gateway token for subsequent transactions. See chapter Gateway tokenization for more details.
Subsequent Transactions
From your server, you can make an HTTP POST request to EVO Cloud endpoint
/g2/v1/payment/mer/{sid}/payment
and specify the additional parameters below.
| Parameter | Required | Description |
|---|---|---|
paymentMethod.recurringProcessingModel | O | This indicates whether a transaction is a Credential on File (COF) or a recurring transaction. COF: The consumer initiates a payment, and the merchant prompts the consumer to store the credential on file for future cardholder-initiated purchases. |
paymentMethod.isSubsequentTxn | O | This indicates whether the transaction is a subsequent transaction. This parameter is only used when paymentMethod.type is card. |
The subsequent transactions may also require authentication. See chapter Authentication for more details.
