Card Test Environment: What It Is and How to Use It
A card test environment lets you simulate card payments with test credentials and test card numbers, with no real card data and no real money moving.
Redeem your gift cards at any of our Merchants
Onyx Gift Cards is a Grenadian company designed to introduce, market and manage gift cards systems in Grenada for retailers and corporations. We are enthusiastic about the effect and influence we will have on the local market. We intend to expand our systems regionally with a range of product offerings and services.
Gift cards are the preferred way of giving and receiving gifts. They carry a monetary value that can be redeemed for gifts at your favorite store.
Onyx GiftCards are “Open Gift Cards” which means that they can be redeemed at multiple merchant locations. They are standard credit card size, can fit into the average wallet and made of PVC plastic. Onyx GiftCards are Barcoded for security and safety for the consumer and bear a disclaimer at the back.
Onyx Giftcards can be bought with a branded Card backer which is black in colour and is designed to fit the card. There is an area to write a brief message to the recipient as well.
You do not buy fake credit card numbers for testing. Every major processor publishes its own set of sandbox card numbers, and those published numbers are the correct choice because each one maps to a documented response in a documented environment. What you actually spend money on is a test account or a maintained test suite that covers the cases your free sandbox misses: regional acquirer behavior, specific decline codes, 3D Secure challenge flows, and tokenization. If a vendor offers to sell you a list of "working test cards" with no gateway attached, that is not a test product. Walk away.
The generic approval number is the one everyone quotes, typically a 16-digit PAN that passes the Luhn check and accepts any future expiry date and any three-digit CVV. It proves your form submits. It does not prove your decline handling works.
Each decline number is bound to one reason code. Confirm the processor documents both the PAN and the error string it returns, because your UI copy is driven by the error string, not the number.
Some sandboxes accept any three digits. Others require a specific value for a match and a different value for a mismatch. Read this before you write test assertions, or you will chase failures that are not bugs.
Look for numbers that trigger challenge, exemption, and failure separately. European traffic in particular needs the challenge path tested end to end.
No. A sandbox PAN is routed to a test environment and is rejected by any live gateway. If it appears to succeed on a live site, something is badly misconfigured and you should report it, not exploit it.
Inside a documented developer sandbox, yes. On a live merchant account, no. The intent and the system you point at are what separate a test from fraud.
Do not. Test environments get cloned, logs get shipped to analytics, and the habit carries into production code. Mask or drop the value.
Ask their support team for a test PAN mapped to that code, or switch to a sandbox that documents it. Paying a third party for a mystery number set is never the answer.