Page Comparison

...

In this resource we outline best practices for the following Recurring Transaction use cases:

1. New CoF (Card-on-File)

2. Existing CoF (Card-on-File)

3. Imported CoF (Card-on-File)

To properly identify a transaction as recurring the following steps need to occur:

1. A An authorized transaction needs to be submitted to Payrix with CVV. If available AVS should also be included for validation. The first transaction should be submitted as traditional eComm either a $0.00 Auth or for the first recurring transaction amount. After this, all subsequent transactions will be submitted as recurring. This authorized transaction is referred to as the initial transaction.
   cofType: N/A
   origin: 2/eCommerce

2. The card information needs to be tokenized. The token can be created after the original transaction is authorized using the card data or embedded within the authorizing transaction request.

3. Submit subsequent recurring transactions with the token and initial transaction.
   cofType: scheduled
   origin: 2/eCommerce
   token: {Token ID}
   firstTxn: {Txn ID from Initial Transaction}

...