Testing

This guide explains:

How the Acclaim test environment behaves
How to use test cards and test bank accounts
How to test the full flow from tokenization to payment requests and webhooks

Test environment overview

The Acclaim test environment is designed to behave as close to production as possible, with a few key differences.

No real charges are made. Test cards and bank accounts never pull or deposit real funds.
Same API base URL:
https://api.withacclaim.com/v1
You switch between test and live using different API keys.
Separate API keys. Use test keys from the Acclaim Console when running automated tests.
Lifecycle and webhooks. Payment requests in test mode still move through lifecycle states and emit webhooks so you can verify your handling logic.

Test card details

In the test environment you can use special card numbers to simulate different outcomes. Expiry dates and CVC values are usually flexible, as long as the date is in the future.

Scenario	Brand	Card Number	Expiry	CVC	Result
Successful payment	Visa	4242 4242 4242 4242	Any future	123	Succeeds
Successful payment	Mastercard	5555 5555 5555 4444	Any future	123	Succeeds
Successful payment	Amex	3782 822463 10005	Any future	1234	Succeeds
Successful payment	Discover	6011 1111 1111 1117	Any future	123	Succeeds
Successful payment	JCB	3566 0020 2036 0505	Any future	123	Succeeds
Successful payment	Diners Club	3056 9309 0259 04	Any future	123	Succeeds
Insufficient funds	Visa	4000 0000 0000 9995	Any future	123	Fails insufficient funds
Insufficient funds	Mastercard	5200 8282 8282 8210	Any future	123	Fails insufficient funds
Generic decline	Visa	4000 0000 0000 0002	Any future	123	Generic decline
Generic decline	Mastercard	5105 1051 0510 5100	Any future	123	Generic decline
Generic decline	Discover	6011 0009 9013 9424	Any future	123	Generic decline
Incorrect CVC	Visa	4000 0000 0000 0127	Any future	000	CVC failure
Incorrect CVC	Mastercard	5555 5555 5555 5557	Any future	000	CVC failure
Requires authentication (3DS)	Visa	4000 0000 0000 3220	Any future	123	Moves to `requires_action`
Requires authentication (3DS)	Mastercard	5200 0000 0000 0106	Any future	123	Moves to `requires_action`
Card not supported	Visa	4000 0000 0000 0069	Any future	123	Not supported / unsupported method error
Card not supported	Amex	3787 3449 3671 000	Any future	1234	Not supported / unsupported method error
Fraudulent card test	Visa	4000 0000 0000 9979	Any future	123	Fails fraud checks
Fraudulent card test	Mastercard	5155 5555 5555 5557	Any future	123	Fails fraud checks

How to use test cards

Create a tokenization request for your test payer.
Load the Payment Element in your UI using the tokenization request.
Enter one of the test card numbers with a future expiry and CVC.
Complete the flow and observe how the payment method and subsequent payment requests behave.

Use different cards to validate:

Successful flows
Declines and error messages
3DS or additional authentication flows

Test bank account details

For bank based payment methods (for example ACH or SEPA) you can use special test account details. These accounts never move real money but are accepted by the sandbox as valid instruments.

Example US ACH test accounts

Scenario	Routing number	Account number	Account type	Result
Successful debit	110000000	000123456789	checking	Payment succeeds
Insufficient funds	110000000	000000000001	checking	Payment fails insufficient funds
Account closed	110000000	000000000002	checking	Payment fails account closed

Example EU SEPA test IBANs

Scenario	IBAN example	Result
Successful debit	DE89370400440532013000	Payment succeeds
Rejected mandate	DE89370400440532013001	Mandate or debit is rejected

Use these IBANs or your configured equivalents when testing SEPA collection flows for Collect.