Choose from any of our gift cards to give to your loved ones
Card Testing Software for Merchants: A Comprehensive Guide
Redeem your gift cards at any of our Merchants
You can purchase a gift card from any of these locations
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.
Card test software is any tool that submits payment credentials to a system to check whether a transaction would be approved. Developers rely on it to validate checkout flows in a sandbox before a site goes live. Criminals use the same concept at scale to check whether stolen card numbers still work, which is why a sudden burst of small declined charges is treated as a fraud warning sign.
At its core, the software sends a card number, expiration date, and security code to a payment endpoint and reads the response. The response codes matter more than the charge itself. A test tool maps out which combinations produce approvals, declines, or errors.
Common functions include:
Every major processor publishes test card numbers and test API keys. Those numbers are designed to fail in production, so a developer can exercise an entire payment flow without touching a real account. Good practice is straightforward: keep test keys out of production code, never paste live card data into a staging environment, and confirm that your logging does not retain full card numbers.
Card test software in this context is really integration testing. It belongs in a continuous integration pipeline alongside unit tests, so a payment flow change cannot ship without proof that approvals, declines, and refunds still behave correctly.
Card testing fraud works by brute force. An attacker takes a list of card numbers, runs a large number of low-value transactions, and keeps the ones that return an approval. The merchant absorbs the cost of the declines, the processor fees, and any chargebacks that follow.
Signals that a merchant is being targeted include many different card numbers used from one device or IP address, a spike in small authorization attempts, mismatched billing geography, and repeated attempts within a short window. Payment networks publish guidance on this pattern under names like card enumeration or account testing.
Fraud prevention is cheaper than remediation. Chargebacks, network monitoring fees, and account termination risk all follow a successful card testing run.
Testing payment systems with card data you do not own is illegal in most jurisdictions, regardless of whether the transaction settles. Card data handling also falls under PCI DSS, which applies to any system that stores, processes, or transmits account numbers. Use your own cards, or use the sandbox numbers your processor provides. There is no third path that is both safe and lawful.
