Store vouchers and member benefits
Connect voucher issuance, holdings and redemption to store and customer systems.
The scenario
ForRetailers, hospitality businesses and membership teams
Issue five drink vouchers to a customer and redeem one during a visit. Keep purchase records in the store system and map unused quantities and usage to token records.
What this makes visible
Customers can see remaining vouchers, while the store traces purchases, redemptions and unused quantities by member ID.
Token and business-data roles
Represented by tokens
Represent multiple copies of a voucher type with PrivilegeEdition. Map each type’s conditions to its redemption process.
Managed in business systems
Member/order IDs, payment results, store, voucher type, validity period and usage records.
Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.
Contract composition
| Contract | Role in this use case |
|---|---|
| PrivilegeEdition | Manage quantities by voucher type and consume them on redemption. |
| Whitelist | Restrict participation to eligible members when needed. |
Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.
User and processing flow
Configure a voucher type
Map eligible products, quantity, validity and transfer conditions to operating rules.
Map purchase to issuance
Verify payment, issue five vouchers and link the order to the transaction.
Redeem one in store
Check product eligibility and holdings, then redeem while preventing duplicate processing of the same request.
Reconcile balance and history
Reconcile one used voucher and four remaining vouchers with store usage records.
Operating considerations
Checks at redemption
Use the authorized redemption request and execution result as evidence, not merely a displayed QR code.
Cancellation and refunds
Separate purchase cancellation from token usage state and retain the handling history under store policy.
Implement this use case
These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.