A debit card test v6 is a versioned set of test card numbers that developers use in a payment sandbox to run debit transactions without moving real money. Each number passes format checks like the Luhn algorithm, then returns a scripted result such as approved, declined, or insufficient funds.
What does the "v6" label mean in a test card set?
Payment providers ship their test cards in releases. A v6 set is the sixth revision of that group, and it changes when the provider adds card networks, 3-D Secure flows, or new decline codes.
Read the version as documentation, not as a feature. If a tutorial cites debit card test v6 numbers and your dashboard shows v5, the older numbers still handle basic approvals but skip newer scenarios.
How sandbox debit card tests work
A sandbox is a copy of the payment API that talks to a simulator instead of a bank. The simulator reads the card number, matches it to a test profile, and returns a fixed response.
- The number passes a checksum so client-side validation accepts it.
- The simulator maps the number to one scenario: success, decline, processing error, or authentication challenge.
- No funds move and no issuer gets contacted.
- Results stay deterministic, so repeated runs return the same answer.
That last point matters for automated tests. You can assert on a specific decline code and trust it tomorrow.
Test cases most debit card suites cover
- Approval: a card that clears authorization with no challenge.
- Generic decline: returns a "do not honor" style code.
- Insufficient funds: a separate code path your UI should show.
- Expired card: checks your date validation and error copy.
- Incorrect CVC: checks that you collect and pass the code.
- Processing error: simulates a network failure or timeout.
- 3-D Secure challenge: forces the authentication step, with pass and fail variants.
Some suites also add debit-specific cases such as PIN-less debit routing or partial approval. Ask your processor which of these the sandbox supports before you write tests around them.
How to run a debit card test v6, step by step
- Switch your API keys to test mode. Live keys will not reach the simulator.
- Pull the current test card list from your provider docs and check the version stamp.
- Map each scenario you care about to one number, and store the pairs in a fixtures file.
- Run the charge, capture, refund, and void calls in that order. Check state changes at each step.
- Replay the same charge twice to confirm your idempotency keys work.
- Log the raw response codes, then compare them to the codes your UI displays.
Keep the fixtures file in version control with a date stamp. Test sets change, and a stale card list breaks a CI pipeline at the worst time.
What a test debit card cannot verify
- How a real issuer handles your transaction. Issuers apply their own risk rules.
- PIN debit networks and ATM behavior.
- Settlement timing and bank statement descriptors.
- Chargeback flows, which need a live dispute process.
Plan a small live pilot with real cards and small amounts before launch. Sandbox passes tell you the code works, not that the money moves.
Common errors and what they mean
- "Invalid card number": a typo broke the checksum. Re-copy the digits.
- Unexpected decline: you grabbed a decline test card by mistake.
- "Authentication required": the number is a 3-D Secure case. Complete the challenge in the test iframe.
- Empty response: your webhook endpoint is down or the test clock skipped the event.
Test numbers are not a way to check real cards
Test numbers work only inside a sandbox. Running real card numbers through a script to see which ones are live is card testing, and it is fraud.
Card testing shows up as bursts of small authorizations, high decline rates, and many cards from one IP address. Visa and the FTC both publish guidance on spotting and blocking it, and processors may freeze an account that shows the pattern.
If you need to verify a card your customer gave you, use your processor vault and its own verification call. Do not guess with test tools.
FAQ
Is it legal to use debit card test v6 numbers?
Yes, when you use them in a sandbox you control as part of development. The numbers are fake and no issuer is involved.
Do test debit cards expire?
Most carry a fixed future expiry date that the provider updates over time. If a card stops working, check the current docs before you debug your code.
Can a test card confirm that a real debit card is active?
No. Test numbers live in the provider simulator and have no link to any bank account.
Why does my test card work in one environment and fail in another?
Each processor runs its own simulator with its own number list. A v6 set from one provider will not match another provider sandbox.