3DS Challenge Card Testing Method Guide
Learn the 3DS challenge card testing method for secure online transactions.
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.
A 3DS card challenge test runs a test card through the EMV 3-D Secure challenge flow in a sandbox. It confirms three things: your 3DS Server builds a valid AReq, the issuer's Access Control Server (ACS) returns transStatus C, and your checkout renders the challenge window and posts the CReq back.
The challenge flow is one of two results. The ACS returns transStatus Y when it authenticates with no cardholder input. It returns transStatus C when the cardholder has to enter a code or approve in an app.
Sandbox ACS rules differ from production rules. A sandbox card that forces a challenge can pass frictionless at a live issuer. Live issuers add risk scores, device fingerprint data, and velocity rules. No test card reproduces those inputs.
18 U.S.C. 1029 covers fraud and related activity with access devices. Running a card you do not own through a live 3DS challenge is a federal offense and breaks card network rules. A merchant can test a live account only with the account holder's consent.
Log the threeDServerTransID, the DS transaction ID, the message version, the transStatus, and the ACS timestamp for every run. Those five fields are what you compare when a production challenge fails.