Skip to content
InsightLogEditorial Notes
菜单

这篇文章尚未翻译成中文,当前显示英语原文。

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.

Sofia Almeida更新于 2026年11月20日阅读 1 分钟阅读 626
分享到 X
好评 100%

核心摘要 · 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:

  1. Was the value issued?
  2. 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

EventQuestion it answersMutates balance
IssuanceWas a card created?No
ActivationIs the card usable?Yes
RedemptionWas value spent?Yes
SettlementDid 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

  1. Balance overwrites instead of append-only ledger entries.
  2. Redemption endpoints that succeed twice for the same key.
  3. No link between activation batches and settlement batches.
  4. 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.

常见问题

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.

这篇文章对你有帮助吗?

你的评价会告诉其他读者这篇文章的可信度。

好评 100%

Sofia Almeida
Sofia Almeida

Payments and crypto reporter · InsightLog

Reports on gift cards, stablecoin rails, wallets and the fraud controls that keep prepaid money honest.

Markdown 原文: /zh/posts/gift-card-api-risk-model/raw

引用来源: https://insightlog.site/zh/posts/gift-card-api-risk-model

Continue reading

延伸阅读