Connecting test payment sources

You can use Crezco's simulators to link fake bank accounts and cards to your organisation. You can then use these payment sources to make payments without moving real money.

Set up a Fake Bank Account

To connect a fake bank account, follow the steps outlined in the account connection guide. When selecting the bank, make sure to select the Crezco Sandbox - GB bank.

Instead of a real bank the app will redirect you to the simulator interface. Here you can select a preconfigured scenario to respond with. By default this is a successful bank connection. When choosing InstantlyCompleted it will then connect two new fake accounts. One will be a savings account and one will be a current account.

Set up a Fake Card

To connect a fake card, call Connect Card (or Connect and choose to add a card) and enter one of the test card numbers below in the hosted flow - see Executing a Simulated Card Payment for the full list. Use expiry 12/2030 and CVV 123 unless stated otherwise.

Executing a Simulated Payment

To make a simulated payment you need to use the id for a fake account when creating a pay run. The checkout flow will then redirect you to the simulator interface instead of a real bank.

The simulator interface allows you to configure various payment results. By default it will configure a successful payment. Once you've finished setting configuration, click Submit to be redirected back as if returning from the users bank.

Modes

Completed - Simulates when funds are taken from the payers account.

Declined - Simulates when the payment is declined by the bank

Insufficient Funds - Simulates when there are not enough funds to facilitate the payment.

Redirect Error - Configured an erroneous response when returning from the bank to the payment flow.

Requires-Multi-auth - Simulates when a payment requires authorisation from multiple parties.

Stuck - This configures the payment to stay in a pending state and never complete.

User Cancelled - Simulates when the end-user cancels the payment authorisation.

Supplementary Behavioural Options

Processing Delay - Allows you to set up to a 30 second delay before the configured response is actioned. The payment will appear as pending until this point. Available for Completed, Declined and Stuck modes.

FX Behaviours - If your payment is (or in the case of bulk payments includes) cross currency payments, you can configure various FX related responses to each one such as conversion failures or payout failures/reversals. Available for Completed and Stuck modes.

Executing a Simulated Card Payment

To make a simulated card payment, set paymentSourceType to Card when creating a pay run and check out as normal - see the Pay by card guide. Instead of a real card processor, enter one of the test card numbers below at the hosted card entry page to trigger the corresponding outcome.

Unless noted otherwise, use expiry 12/2030 and CVV 123.

📘

Reusing a stored test card

If you connect one of these test cards as a payment source first (see Set up a Fake Card), you can also reference it by paymentSourceId on a pay run instead of re-entering the card details at checkout - the same outcome will be simulated.