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
recurringProcessingModelis included, theamountfield can be set to0for card tokenization. (In this case you don't have to follow the minimum amount guidelines)
Accepted Values
| Value | Description |
|---|---|
| CardOnFile | Used when customers initiate payments with their stored payment details for a faster checkout experience. |
| Subscription | Used when merchants initiate recurring payments to charge customers at regular, fixed intervals. |
| UnscheduledCardOnFile | Used when merchants initiate payments at irregular intervals, such as automatic account top-ups or usage-based billing. |
Request Example - Card Tokenization for Future Use
{
"amount": 0,
"currency": "ISK",
"returnUrl": "https://your-ecommerce-website.com/straumur_redirect",
"reference": "9990QQAZ1221",
"recurringProcessingModel": "CardOnFile"
}
Request Example - Card Tokenization with Subscription
{
"amount": 10000,
"currency": "ISK",
"returnUrl": "https://your-ecommerce-website.com/straumur_redirect",
"reference": "9990QQAZ1221",
"recurringProcessingModel": "Subscription"
}
Request Field
| Field | Type | Required | Description | Example | Min Length | Max Length |
|---|---|---|---|---|---|---|
| recurringProcessingModel | String | Optional | Specifies the type of recurring transaction. | CardOnFile | - | - |