Recurring Processing Model

info

This field allows merchants to specify the type of recurring transaction being processed. We support different recurring payment scenarios and provide flexibility for various payment use cases.

Some things to keep in mind:

• If the recurringProcessingModel field is sent, the merchantShopperReference field cannot be used in the same request.
• If recurringProcessingModel is included, the amount field can be set to 0 for card tokenization. (In this case you don't have to follow the minimum amount guidelines)

Accepted Values

Value	Description
CardOnFile	Card details are stored for one-click purchases, omnichannel journeys, or subscriptions with non-fixed schedules.
Subscription	Transactions for fixed or variable amounts following a fixed schedule.
UnscheduledCardOnFile	Unscheduled transactions using stored card details, such as automatic top-ups based on predefined conditions.

Request Example - Card Tokenization for Future Use

{
  "terminalIdentifier": "1adfe4a1",
  "amount": "0",
  "currency": "ISK",
  "reference": "9990QQAZ1221",
  "channel": "Web",
  "origin": "https://www.your-ecommerce-website.com",
  "threeDsReturnUrl": "https://your-ecommerce-website.com/straumur_redirect",
  "recurringProcessingModel": "CardOnFile"
}

Request Example - Card Tokenization with Subscription

{
  "terminalIdentifier": "1adfe4a1",
  "amount": "48900",
  "currency": "ISK",
  "reference": "9990QQAZ1221",
  "channel": "Web",
  "origin": "https://www.your-ecommerce-website.com",
  "threeDsReturnUrl": "https://your-ecommerce-website.com/straumur_redirect",
  "recurringProcessingModel": "Subscription"
}

Request Field

Field	Type	Required	Description	Example	Min Length	Max Length
recurringProcessingModel	String	Optional	Specifies the type of recurring transaction.	CardOnFile	-	-