Standalone Commerce Microsite

Gift Card Voucher System

Start from the QR-order customer account, charge a fixed amount, then either bind the credit to that same wallet or send it onward as a gift for someone else to claim.

This prototype treats customer identity as the source of truth. The PDF, QR payload, R2 key, and email queue are all downstream artifacts of the same customer-linked purchase.

Start Issuing See Fulfillment Path

Previewed Product

$100

Customer-Linked Gift Credit

One QR-order checkout can become self credit or a Christmas gift transfer.

Source
Customer + QR session
State
Wallet or claim link
Trail
PDF + email + R2

Customer binding

QR order account

Every purchase starts from the logged-in customer who opened the ordering QR.

Credit destination

Self or gift

The same purchase can top up the buyer wallet or create a transfer flow for someone else.

Audit trail

PDF + R2 + email

Ops can see the customer link, stored artifact, and outbound notification before backend wiring.

Purchase Studio

Take the QR-order customer, then decide whether the balance stays or travels.

The issuer is always the logged-in ordering customer. From there the same charge can top up the issuer wallet or become a gift another person claims later.

Credit destination

Local mode simulates the paid QR-order checkout, wallet binding, PDF generation, R2 key creation, and either receipt or gift notification.

Fulfillment Path

Operational handoff stays tied to the customer purchase.

Each step below maps directly to the live QR-order flow: paid checkout, wallet binding, PDF archiving, and the outbound receipt or gift notification.

QR order checkout

Charge the logged-in customer first.

A live system would originate from the restaurant QR order session and wait for a paid webhook.

Waiting

Wallet binding

Attach the credit to a customer or a gift claim.

Self purchases bind immediately. Gift purchases create a recipient-facing claim path.

Waiting

PDF archive

Store a formal artifact in R2.

The stored PDF preserves the issuer, wallet destination, and claim metadata for support and audit.

Waiting

Notification

Send the right outbound message.

Receipt email for self top-up, transfer email for gifts, both tied back to the same customer purchase.

Waiting

Wallet Binding

Customer and access path

The issuer, destination wallet, and claim route stay visible for support and ops.

After checkout, the issuer customer, wallet owner, QR session, and wallet or claim URL will appear here.

Notification Queue

Receipt or transfer email

The queued outbound message changes automatically depending on self or gift mode.

After checkout, the email subject, body preview, and attachment metadata will appear here.

Recent Issuance

Latest credits

Recent output is stored locally so the operator can verify each customer-linked issue.

No credits issued yet in this browser session.