Test EBT Cards
Forage SDKs include built-in EBT Card Number validation in both sandbox and production. This guide lists valid EBT test card numbers for developing against successful transactions and invalid EBT test card numbers for triggering exceptions.
Replace any
XXXXXX
s with numbers of your choice.
Valid EBT test card numbers
To exclusively test successful EBT transactions, use any 16-19 digit number starting with 9999
, for example:
9999XXXXXXXXXXXX
9999XXXXXXXXXXXXX
9999XXXXXXXXXXXXXX
9999XXXXXXXXXXXXXXX
All sandbox test cards have $100 SNAP and $100 EBT Cash balances that reset at the end of each day. You can make purchases and refunds using these cards just as you would expect to in production.
Invalid EBT test card numbers
Use the EBT test card numbers in the following sections to trigger specific error scenarios:
Balance inquiry exceptions
Card number | Test case |
---|---|
5555555555555514 | Invalid card number |
5555555555555554 | Expired card |
654321XXXXXXXXXX | Returns $0 for the EBT Cash balance on balance checks. These cards help you test the balance inquiry experience for customers from US states that donβt support EBT Cash. |
Fully Hosted exceptions
Card number | Test case |
---|---|
3333333333333345 | EBT transaction succeeds, but the credit card fails to process during a split tender transaction. |
Payment Capture exceptions
Card number | Test case |
---|---|
4444444444444443 | Lost/stolen card |
4444444444444454 | Expired card |
4444444444444451 | Insufficient funds |
4444444444444455 | Invalid PIN |
4444444444444462 | Card restricted due to fraud concern |
SDK validation exceptions
Card number | Test case |
---|---|
1111111111111111 | Sets the EBT Card Number input validation state to false when entering a number to tokenize (Forage JS, Android, iOS). Use this EBT card number to test error handling event listeners. |
Find more information on handling EBT errors with Forage in the reference documentation.
Updated 17 days ago