Skip to main content
Use these test card numbers to simulate card funding sources and card-based deposits in the staging environment. They let you verify your add-card, deposit, and decline-handling logic without a real card.
Staging onlyThese numbers are accepted only on the staging endpoint (https://transactional-graph.staging.fluzapp.com/api/v1/graphql). They will be rejected in production. See Add Funding Sources for how to attach a card.
How to use these values: pass the number to addBankCard as cardNumber. CVV — any 3 digits (any 4 for American Express). Expiration date — any date in the future. Cardholder name — any non-empty value.
A billing address is required. addBankCard accepts either a billingAddress object or a saved userAddressId. On an account with no address on file, omitting both fails. Use a value from Test Addresses.The same card can only be added once. Re-adding a number already on the account fails with a generic decline rather than a duplicate error, which is easy to misread as the test number being invalid. Check getWallet before retrying, and remove the existing card with deleteBankCard if you want to add it again.

​
Successful Transactions

The cards below simulate successful card transactions.

​
Declined Transactions

The cards below simulate declined transactions. Each returns the listed error code so you can test how your integration surfaces failures. See Decline Codes for the full reference.

​
Next steps

Test bank accounts

Simulate ACH and bank-account funding sources — the other half of testing deposits.

Decline codes

The full reference for every decline reason your integration should handle.
Want to learn more? Contact us at partnerships@fluz.app. Speak with our experts for more info or to request a demo.