Test Your EPaySe Integration in the Sandbox First

The sandbox is a practice version of EPaySe where you can try payments with test cards and no real money moves. Test it before you go live: run one payment that succeeds, one that is declined, and a few error cases. This matters even more when an AI assistant wrote your code, because you did not type every line yourself.
- Sandbox: a practice mode with fake money.
- Test cards: special card numbers that give a chosen result.
- Goal: see both good and bad outcomes work before a real customer pays.
What is the sandbox?
It is a separate copy of the payment system for testing. EPaySe's sandbox has its own web address, which is different from the live one, and it uses test credentials. Payments there are not real, so you can try, fail and try again at no cost.
What are test cards?
Test cards are card numbers published in the EPaySe documentation. Each one gives a known result, for example a successful payment, a decline, insufficient funds, an expired card or a wrong security code. They only work in the sandbox. Look at the test cards page for the list.
What should you test?
- A payment that succeeds. Check that the customer returns to your shop and that the order is marked paid only after EPaySe confirms it.
- A payment that is declined. Check that the customer sees a clear message and can try again.
- A repeated request. Check that clicking pay twice does not create two payments.
- A refund. Check that a refund can be created and that it shows up in your system.
- A bad request. Check that your code shows a useful message when EPaySe rejects something, instead of failing silently.
Why does testing matter more with an AI assistant?
An assistant can write code that looks right and passes a quick glance. The sandbox shows whether it really works. If the assistant misunderstood a rule, such as the amount unit or how to check a confirmation message, a sandbox test usually exposes it in minutes. Run your tests again after every change the assistant makes.
How do you keep testing safe?
Use sandbox credentials only while building. Keep the live secret key out of your project files and out of chats with the assistant. See keep your EPaySe secret key away from your AI assistant. Our payment integration testing checklist lists more cases worth trying.
EPaySe is an early-stage payment gateway, still in development, so the sandbox is the right place to start. Read the documentation for the details.
Key takeaways
- The sandbox is a practice mode with no real money.
- Test a success, a decline, a repeat and a refund.
- Re-test after every change an AI assistant makes.
- This is general education, not legal or financial advice.
Questions? Contact the team.
FAQ
What is the EPaySe sandbox?
It is a practice version of EPaySe with its own address and test credentials, where payments are not real and no money moves.
What is a test card?
It is a card number from the documentation that gives a chosen result in the sandbox, such as success or decline. It does not work on live payments.
Do I need to test if an AI assistant wrote the code?
Yes. Testing is how you find out whether the code really follows EPaySe's rules, so run the tests again after every change.
Can I use my real cards in the sandbox?
No. Use only the test cards from the documentation.
What should I test before going live?
A successful payment, a decline, a repeated request, a refund and a rejected request.
Related Articles

Go-Live Checklist for a Checkout Your AI Assistant Built
Before real customers pay, read every line, re-run every test, move the live key to your server settings and start with one small order. A short checklist for AI-built checkouts.

Mark Orders Paid Only After EPaySe Confirms
The page a customer returns to is not proof of payment. Learn how EPaySe's confirmation message works, how to check it, and why AI-written code often gets this part wrong.

What to Check in Payment Code Your AI Assistant Wrote
An AI assistant can write payment code that looks right but breaks on small details. Here are the checks that catch the most common EPaySe integration mistakes, in plain words.

Keep Your EPaySe Secret Key Away From Your AI Assistant
Your secret key proves that a request comes from your shop. Learn why it must never go into a chat, where to keep it instead, and what to do if it leaks.