Recurring Payments is a MultiSafepay solution that securely stores payment details to enable quick, easy repeat payments.
MultiSafepay encrypts customers' sensitive payment details during an initial payment for secure storage, and provides you with a non-sensitive identifier for the details known as a “token”. Customers can save multiple tokens.
Subsequent payments are exempt from SCA and 2FA. MultiSafepay is responsible for PCI DSS compliant storage of payment details.
Tokens are stored at account level rather than website level. If you operate multiple websites from a single MultiSafepay account, you can also offer cross-domain recurring payments, i.e. tokenize a customer’s details on Website A and offer one-click payments on Website B.
Optionally, you can set the amount for the initial payment 0
. No funds are transferred but a token is created (if the payment details are valid).
See Zero Authorization.
MASTERCARD **43
.This is also known as “one-click payment”.
There are two common use cases for merchant-initiated subsequent payments:
Email a request to activate Recurring Payments to [email protected]
Specify in your request which tokenization model(s) you want to use:
We send you an agreement to sign, including terms and conditions for data usage.
MultiSafepay offers three recurring models:
cardOnFile
(one-click payments)subscription
unscheduled
(event-triggered)Our API and PHP SDK support all three models.
Our ready-made integrations use cardOnFile
only.
You must have both credit card payments and recurring payments enabled for your MultiSafepay account.
We support recurring payments in our plugins for:
See API reference – Create order > customer.reference
.
Note: Tokens for SEPA Direct Debit transactions are originally received as iDEAL or Sofort transactions.
Parameter | Type | Description |
---|---|---|
type |
string | The payment flow for the checkout process. Options: direct , redirect . |
gateway |
string | The unique gateway_id to redirect the customer to the specific payment method. Make a get gateway request. |
Options: AMEX , VISA , MASTERCARD , DIRDEB . |
||
recurring_id |
string | A randomly generated recurring ID for the customer. |
reference |
string | The customer’s reference number for the token. |
recurring_model |
string | The type of recurring model to use. Options: unscheduled , cardOnFile , subscription . |
Feedback
Propose a change on GitHub
or
send an email to [email protected]
Other languages
For an explanation in another language, contact your account manager.