Card Expiry Test: A Comprehensive Guide to Buying CVV
Discover the importance of the card expiry test in buying CVV and how it ensures security.
Our Cards
Choose from any of our gift cards to give to your loved ones
Choose from any of our gift cards to give to your loved ones
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.
An Authorize.net test card is a published card number that works only inside the Authorize.net sandbox, where it simulates a payment without moving money. You use these numbers to run charges, voids, refunds, and address verification checks before your integration handles real transactions. Test numbers are not real cards, and they are rejected by the live production gateway.
The sandbox is a separate environment from the production gateway. It mimics the response format of a live transaction, but it never contacts an issuing bank. Because of that, it needs card numbers that the gateway recognizes as test data. When you submit an Authorize.net test card, the sandbox returns a simulated approval or decline, along with a transaction ID you can use for follow-up actions such as void and refund testing.
This setup keeps real card data out of your development workflow, which matters for PCI compliance. Live card numbers should never be typed into a test environment.
The developer documentation publishes a list of numbers by card brand. Widely used examples include:
Each entry on the official list is paired with the response it produces, so check the current documentation before you build assertions around a specific number. Authorize.net occasionally updates its sandbox behavior.
For most test numbers, any future expiration date works. A common choice is a date several years ahead so the test data does not expire mid-project.
If a transaction fails while you expect an approval, check the expiration year first. A past date produces a decline that looks like a gateway error but is simple to fix.
An integration that only ever sees approvals is not tested. The sandbox lets you trigger the responses your code must handle: a generic decline, an expired card, a CVV mismatch, and an address verification mismatch. The developer documentation lists the card numbers tied to each response code, and you can also use the sandbox account settings to force a specific outcome for a transaction.
Build your test cases around the response codes your application acts on, not around the card numbers themselves. That way the tests stay useful when the list of Authorize.net test cards changes.
Confirm that approvals, declines, voids, refunds, and error handling all behave as expected in the sandbox. Then swap the API login ID and transaction key for the production credentials, point your endpoint at the live gateway, and place one small real transaction. The Authorize.net test card has done its job once your code handles every response without a manual fix.