What a gift card balance can and cannot prove
A prepaid balance is a liability entry, not a receipt. Model gift card APIs so issuance, redemption and settlement stay auditable.
Key summary · TL;DR
A gift card balance proves that value was loaded and has not been spent yet. It does not prove who owns the card or that the cash was collected. Reliable gift card systems separate issuance, activation, redemption and settlement into distinct, idempotent events.
Key facts
- Issuance, activation and redemption need separate events with their own audit records.
- Balance reads must never mutate redemption state.
- Partial redemption and refunds belong in an append-only ledger, not in balance overwrites.
A balance is a liability, not a receipt
Gift cards look simple: load value, spend value. In production, a balance is a liability entry, not proof of payment. Two questions get mixed together:
- Was the value issued?
- Was the cash collected and settled?
An API that only answers the first question cannot support finance, disputes or fraud review.
Separate the four events
| Event | Question it answers | Mutates balance |
|---|---|---|
| Issuance | Was a card created? | No |
| Activation | Is the card usable? | Yes |
| Redemption | Was value spent? | Yes |
| Settlement | Did the cash arrive? | No |
When these events share one endpoint, a failed settlement looks identical to an unactivated card.
Idempotency is the security control
Every redemption call needs a client-generated idempotency key. Without one, a retry after a network timeout can double-spend a card. Store the key next to the resulting ledger entry and return the original response when the key repeats.
What to expose
- A signed balance snapshot with currency, as-of time and event id.
- A ledger endpoint filtered by card and time range.
- A redemption endpoint that returns both the new balance and the ledger entry id.
Never expose internal card numbers or full primary account numbers. Use tokenized references and scope them per merchant.
Red flags in review
- Balance overwrites instead of append-only ledger entries.
- Redemption endpoints that succeed twice for the same key.
- No link between activation batches and settlement batches.
- Timestamps without a timezone.
Conclusion
Treat a gift card as a small financial ledger. The API is trustworthy when every balance change has an event, an idempotency key and an audit trail.
Frequently asked questions
Is a gift card balance a guarantee of funds?
No. It is a recorded liability. Whether the cash was actually collected depends on the settlement ledger, which is a separate system of record.
Should the API return a raw balance?
Return a signed snapshot with currency, an as-of timestamp and an event id so clients can detect stale or replayed data.
Was this article helpful?
Your rating tells other readers how reliable this article is.
Payments and crypto reporter · InsightLog
Reports on gift cards, stablecoin rails, wallets and the fraud controls that keep prepaid money honest.
Markdown source: /en/posts/gift-card-api-risk-model/raw
Cite this article: https://insightlog.site/en/posts/gift-card-api-risk-model
Continue reading
Read next
Designing content for the GEO and AEO era: from search engines to answer engines
Owning search results pages is no longer enough. Here is how to structure content so generative engines can cite it.
Gift card fraud signals that survive a manual review
Gift card fraud rarely looks like one stolen card. It looks like small behavioural deviations across velocity, devices, geography and timing.