When you’re building an integration with the API, there are some common paths you should make sure your integration handles successfully, for example a customer cancelling their mandate or a payment failing due to lack of funds.

In the sandbox environment, we provide scenario simulators: special customer names that trigger these sequences of events almost instantly. For example, if you create a customer with the given_name “Successful”, their payments will succeed immediately.

These customer names take effect only on payments created manually, not those created through a subscription.

All the relevant events and webhooks will be created and sent for these transitions.

Customer given_name Description What happens on mandate creation What happens on payment creation Schemes supported
Successful The customer’s payment is collected successfully and paid out to you. The mandate is marked as submitted, then activated. The payment is marked as submitted, then confirmed. If you’ve set up a creditor bank account, it is then paid_out and a payout is created. Bacs, SEPA Core and Autogiro
Penniless The customer’s payment can’t be collected, for example because they don’t have enough money in their account. The mandate is marked as submitted, then activated. The payment is marked as submitted, then failed. Bacs, SEPA Core and Autogiro
Fickle The customer’s payment is collected successfully, but is then charged back by the customer disputing it with their bank. The mandate is marked as submitted, then activated. The payment is marked as submitted, then confirmed. If you’ve set up a creditor bank account, it is then paid_out and a payout is created. Finally, the payment is marked as charged_back. Bacs, SEPA Core and Autogiro
Late The customer’s payment can’t be collected, but the bank informs us of the failure later than normal. The mandate is marked as submitted, then activated. The payment is marked as submitted, then confirmed, then failed. Bacs, SEPA Core and Autogiro
Invalid The customer’s mandate can’t be set up because their bank details are rejected by the banks as invalid. The mandate is marked as submitted, then failed. N/A Bacs, SEPA Core and Autogiro
Expired The customer's Bacs or SEPA mandate has expired because no collection attempts were made against it for longer than the scheme's dormancy period (13 months for Bacs, 3 years for SEPA). The mandate is marked as submitted, then activated, then expired. N/A Bacs and SEPA Core
Switching The customer has an existing Bacs mandate which is transferred to another bank account using the UK’s Current Account Switching Service. The mandate is marked as submitted, then active, then transferred. N/A Bacs only
For SEPA mandates, “what happens on mandate creation” will only occur when the first payment is taken.

You may also want to test the scenarios where a payment or mandate is cancelled. You can cancel payments and mandates in one click on your dashboard, or via the API (see the guide for an example).

In the sandbox, you can set up payments using our test details:

  • In the UK use the sort code 200000 and the account number 44779911
  • In Sweden, use the clearingnummer (branch code) 5491, the kontonummer (account number) 0000003 and the personnummer (Swedish identity number) 198112289874
  • Everywhere else, use the French IBAN FR1420041010050500013M02606

You can find more country-specific bank details in our appendix.

Test webhooks →