How to choose Recurring Processing Model?
The recurringProcessingModel defines a recurring payment type. By default the recurringProcessingModel is set to Subscription. You can change the recurringProcessingModel on merchant account level. This will apply to all (recurring) transactions from your account. If you want to set the Recurring Processing Model on a transaction level, you should submit the values on your API request. Possible values are:
- Subscription: Contracts for a series of transactions with fixed or variable amounts, following a fixed time interval. If not set in the payment request, this will be the default value for shopperInteraction ContAuth.
- CardOnFile: Models where a shopper stores card details and then purchases from the website or app at a later time using the stored card details.
- UnscheduledCardOnFile: Contracts that occur on a non-fixed schedule and/or have variable amounts using stored card details. For example, automatic top-ups when the cardholder's balance drops below a certain amount.
The following table shows common business models with the corresponding Payment request parameters (Shopper Interaction and Recurring Processing Model).