Choose from any of our gift cards to give to your loved ones
paypal sandbox card test process
Redeem your gift cards at any of our Merchants
Using the PayPal Sandbox Card Test Tool: A Comprehensive Guide
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.
PayPal's sandbox is the top pick for testing PayPal checkout flows, and the test card numbers you need are generated inside your own PayPal Developer account rather than copied from a public list. This guide compares the sandbox test card tools from PayPal, Stripe, and Braintree against four criteria: how the numbers are issued, which decline scenarios you can reproduce, whether 3D Secure and wallet flows are covered, and how fast you can reset a sandbox that has drifted into a broken state.
PayPal keeps sandbox traffic on a separate network from live payments. When you create a sandbox business account in the Developer Dashboard, you also get test cards tied to that account. The dashboard builds Luhn-valid numbers for the card brands you select, and you can edit the card type, billing country, expiry date, and postal code. Changing those fields is how you trigger declines without touching the number itself. A card dated last month fails as expired. A billing ZIP that does not match the sandbox account country fails an address check.
Some failure modes cannot be reached by editing fields. Those sit behind specific preset numbers published for advanced card processing tests. Treat the generated cards as your baseline and the presets as your edge cases.
Use this as your primary source if you ship a PayPal-hosted checkout, subscription billing, or a saved card on file.
Reach for this when your integration runs two processors and you want fast regression coverage on the card side alone.
Pick Braintree cards if you run your own gateway and add PayPal as a wallet option at checkout.
Bottom line: generate your cards in your own PayPal Developer account, keep a short written record of which number covers which scenario, and only open the Stripe or Braintree card lists when you are testing those gateways. Never type a real card number, real security code, or real billing address into a sandbox. Test data belongs in test environments, and live cardholder data belongs only in a compliant production flow.
