How It Works

A single purchase, traced end to end.

Every SnappyPay transaction is the purchase of a one‑time digital redemption code from SnappyPay Systems. The amount is set by the customer’s checkout total. The code is delivered, applied, and invalidated within the same purchase event.

The Purchase Event

Five stages, one transaction.

The diagram below maps a single end‑to‑end purchase. The card transaction is the customer’s purchase of a digital good from SnappyPay Systems.

  1. 01

    Customer at checkout

    Customer selects the SnappyPay option on a participating merchant site.

  2. 02

    Purchase initiated

    Customer purchases a digital redemption code from SnappyPay Systems for the checkout amount.

  3. 03

    Card tokenized

    Card details are captured in a PCI‑DSS Level 1 service. SnappyPay receives a token, never the PAN.

  4. 04

    Purchase confirmed

    Cardholder confirms intent through an out‑of‑band link to a verified contact.

  5. 05

    Code issued & applied

    The code is generated, delivered, applied to the checkout and invalidated. A receipt is sent.

Stage by Stage

Each stage, explained.

What happens at each step, what the customer sees, and what SnappyPay is doing behind the scenes.

1

Customer at checkout

A customer shopping on a participating merchant’s website reaches checkout and is presented with the option to complete the purchase via a SnappyPay digital redemption code. The amount of the code mirrors the customer’s checkout total exactly.

2

Purchase initiated

The customer purchases a one‑time digital redemption code directly from SnappyPay Systems. The card transaction is between the cardholder and SnappyPay Systems. There is no parallel charge from the participating merchant.

3

Card tokenized

Card details are captured inside a secure iframe served by an external PCI‑DSS Level 1 service provider. The provider returns a token to SnappyPay. The raw card number never reaches SnappyPay’s servers.

4

Purchase confirmed

The cardholder is sent an out‑of‑band confirmation link to a verified email address or mobile phone number. Clicking the link confirms intent to complete the purchase. This produces an independent, time‑stamped record of cardholder authorization.

5

Code issued and applied

SnappyPay generates the unique redemption code, delivers it to the participating merchant’s checkout flow, and applies it to the customer’s purchase. The code is invalidated immediately upon application. A receipt identifying SnappyPay Systems is sent to the customer.

6

Receipt and support

The customer receives an email receipt identifying SnappyPay Systems as the merchant of record. Support is available through the channels listed on the receipt for any questions about the purchase.

Code Lifecycle

Generated, applied, invalidated.

Every redemption code exists only for the purchase it was created to support.

Generated Unique to the transaction. Tied to a specific checkout amount, customer, and participating merchant.
Delivered Delivered electronically into the checkout flow. Not displayed to the customer for external use. Not stored on the customer’s device or account.
Validated Checked at the moment of application for validity, amount match, and redemption status.
Applied Applied once, to the specific checkout it was generated for.
Invalidated Marked as redeemed immediately upon successful application. Cannot be reused, transferred, exchanged, or converted to cash.

Codes have no existence outside the purchase they were issued for. They are not a stored balance, not a reloadable instrument, and not a transferable asset. They are a single‑use digital good consumed at the moment of the purchase event.

Common Questions

Frequently asked.

Who am I actually buying from?

SnappyPay Systems is the merchant of record for the digital redemption code. Support is reachable directly at 1-877-210-1090.

What did I actually purchase?

You purchased a one‑time digital redemption code from SnappyPay Systems. The code was generated for the exact amount of your checkout at the participating merchant, applied to that checkout, and then invalidated. It cannot be reused.

Why do the amounts vary?

The redemption code amount mirrors your checkout total at the time of purchase. Different checkouts produce different code amounts. The code is generated for the specific transaction and is not a fixed‑denomination product.

Can I save my code and use it later?

No. Codes are generated for a specific checkout and invalidated upon application within that same purchase event. There is no stored balance, no reloadable value, and no way to apply a code to a different purchase.

Where can I use a SnappyPay code?

Codes are only redeemable within the closed‑loop participating merchant network, and only against the specific checkout they were generated for. Codes have no use, value, or function outside this purchase event.

Is my card information stored by SnappyPay?

No. Card details are captured and tokenized by an external PCI‑DSS Level 1 service provider. SnappyPay Systems holds only a tokenized reference and never receives, transmits, or stores raw card numbers.

How do I get a receipt?

A receipt is emailed to the address you used at checkout. The receipt identifies SnappyPay Systems as the merchant of record, shows the transaction amount and a customer support contact.

How do I contact support?

Email Support@SnappyPay.com or call 1-877-210-1090. Support hours are Monday through Friday, 8:00 AM - 8:00 PM Eastern. Email responses within one business day.

A checkout screen showing card entry and cart contents
1. Customer selects SnappyPay at checkout
A transaction confirmation on screen
2. Code is generated and applied
A parcel delivered at a door
3. Order completes as normal
Behind the scenes

The code is issued, applied and invalidated in one purchase event.

Nothing is left outstanding for the customer to redeem later, and the merchant never handles the card transaction.

Server infrastructure

Questions about a purchase or the platform?

Our support team is available to help with receipts, transaction questions, refunds, and security concerns.