Recurring card payments
We refer to recurring payments when the platform repeatedly charges the end user’s card at regular intervals for the goods and/or services provided.
Learn more about recurring payments →The recurring card payments feature is testable in Sandbox and a specific set of mocks has been developed to simulate the errors that occur when working with recurring objects.
1. Select the pay-in to which the mock is going to apply
You can use the mock for a customer-initiated or a merchant-initiated transaction.
To do so, you may use the Create a Recurring PayIn Registration endpoint, and use the 33501
value in one of the following Amount
parameters in the body of the request:
FirstTransactionDebitedFunds
to test an MITNextTransactionDebitedFunds
to test a CIT
2. Choose the error to simulate in the recurring registration
You can use the value below in the AddressLine2
parameter of the Billing
object in your recurring pay-in registration body.
AddressLine2 value | Simulated case | Returned error code |
---|---|---|
01100 | Failed pay-in | 101101 |
01116 | Failed due to card limit reached | 101199 |
01125 | Failed due to inactive card | 101106 |
01131 | Reauthentication request from the bank (MIT only) | 101305 |
03022 | Failed SCA (CIT only) | 101301 |
3. Make the recurring pay-in
Make the pay-in (MIT or CIT) with the Create a Recurring PayIn endpoint with the amount of 33501
for the DebitedFunds
.
Example
In this example, we simulate a failed merchant-initiated transaction due to an inactive card by following these steps:
- Create a Recurring PayIn Registration with the mock values
- Create an initial CIT for the authentication
- Create an MIT which will fail, returning the 101106 error.
Note - Mocks available in Postman Collection
The Mangopay API Postman Collection contains the full flow for the recurring mocks to help you test faster.
Was this page helpful?