Web preview module; real provider verification remains separate. Vouchers is separately enabled and permissioned. It uses shared Orders, seller Payment Profiles, customer contact snapshots, artwork and governed transactional email. Buying or receiving a voucher does not join Loyalty, merge customer identities or grant marketing consent.
Products, publication and embeds
Open Vouchers → Products and New voucher. Set the card name, description and optional JPEG/PNG/WebP artwork. The initial quick amounts are £20, £40, £60 and £100; edit them and choose whether customers may enter a custom amount. Minimum and maximum values are in pounds. Choose All venues in this business, Specific venues, or Across businesses. A group administrator with voucher management access can select the selling business and up to 24 other businesses in the same group with Vouchers enabled. Each accepting business still requires its own staff redemption permission. The product library groups cards into an all-venue collection and named venue collections, with search and a scope filter. A published card stays in its published venue collection while saved changes await publication; the card labels those changes separately. Group-wide collections list their accepting businesses. One business sells the voucher and owns its payment, shared balance, refunds and corrections; the ledger records which business accepted each redemption. This does not transfer money between businesses or settle their internal accounts. The accepting set is frozen at purchase: later additions do not gain access to old gifts. Membership, module availability and staff authority are checked again when accepting a voucher. Foreign-business code lookup reveals no purchaser or recipient contact details. A retired accepting scope before payment blocks checkout; retirement during payment enters the existing refund/reconciliation flow. Set a validity period in days or leave it empty for no expiry. Customer terms, a ready GB/GBP seller Payment Profile and voucher VAT treatment are required before publication. Confirm the voucher VAT treatment explicitly before publication. Single-purpose vouchers require an active VAT rate.
Save draft retains edits; Publish explicitly creates an immutable public version. Saving later edits does not replace the published version. Each purchase accepts one exact version and freezes its terms, amount, seller, tax and venue rules. Pause sales prevents new purchases while issued vouchers retain their recorded balances and terms.
Each saved product’s Embeds action opens its own placement library. Embeds also stores a named selection of one voucher product or a collection of up to 20 products from the same business. Copy its saved iframe code or open its saved preview. Draft and practice products are excluded from standard public embeds. Disable and re-enable update the saved embed. Installed snippets continue to use the same public identity.
Each embed card shows Loaded on with up to three https websites that framed it and when each was last seen, or Not seen on any website yet. The visitor's browser reports this, at most every six hours per website and for up to 20 websites per embed; a full list replaces only a website unseen for 30 days. It is an install hint, not proof: a direct link to the embed is not recorded. A disabled embed has Delete, which names the last website seen and needs the embed's exact name typed. Deletion is permanent; a website still using the code then shows that vouchers are unavailable. Issued vouchers, balances and purchases are unchanged. The embed that runs customer voucher accounts cannot be deleted. The initial embed uses image cards; Ticketing’s calendar and Event-specific options do not apply. Public embed identity grants no access to customers, purchased voucher codes or staff actions.
Create a voucher draft
Open Vouchers → Products → New voucher. Enter the name and description, set the amounts and accepting venues, then choose Save draft. Publishing is a separate step and requires the seller payment profile, customer terms and VAT treatment.
Customer card designer
In a voucher product, Customer card designer → Let customers personalise their card enables a small editor in its embed purchase flow. Select the available Classic, Celebrate and Sunshine styles and optionally Allow a customer photo. Classic is a framed serif letter, Celebrate a bold ticket with a confetti panel, and Sunshine a postcard with a split photo or sunburst. Business branding accepts an optional logo from that business’s public media. No logo is required. A logo with a transparent background sits directly on the card in the card’s text colour: white on dark cards, black on light ones. A logo with its own solid background keeps its original colours on a light plaque. Group-wide gift cards do not automatically display the group or issuer name; they list accepting businesses. Checkout still identifies the legal seller. Existing products keep their current purchase flow until this option is enabled and published. Staff still need voucher management access; customers need no Studio account or module access. Save and Publish remain separate.
Customers see a live card preview showing the chosen amount; a custom amount appears once it is within the product's limits. They choose an allowed style and custom card colour (or restore the design colour). Text on that solid colour automatically uses the higher-contrast black or white; photos remain separate from text. Add a heading of up to 100 characters over three lines and an optional 500-character message. If allowed, they can pick a JPEG, PNG or WebP photo up to 5 MB and 16 megapixels, adjust its position, replace it or remove it. Unsupported files show an error without discarding the previous photo. The venue's product name, value, issuer, terms, redemption rules and code cannot be edited. The optional logo and customer design are frozen when the customer continues to payment and appears on the paid purchase, private gift page and printed card. There is no free-form canvas or generated artwork.
Photos are resized and decoded again on the server with embedded metadata removed. Payment waits for the exact photo to be saved; a failed upload retries the same purchase and image. When preparing the voucher or starting payment fails, the customer sees plain copy, never server error text, and can retry or reload to start over. A photo belongs only to that private gift and is not added to the public catalogue or venue media library. Private photo reads require the matching purchase token or issued voucher code. Abandoned uploads with no payment attempt are removed after the purchase expires plus 24 hours; paid gifts and unresolved payment attempts retain their photo. A private photo that cannot load offers Retry photo. Desktop/mobile web and print share the card; this does not add a native editor. Provider checks are still required.
The issued-voucher email uses the ticket email layout and shows the customer's card style, colour and heading, then the value, validity, code and View your voucher, which opens the QR code and balance. Email never carries the private photo; the card shows the style's decorative panel and says the photo is on the voucher page. The recipient's copy adds the buyer's message; the buyer's copy adds the payment receipt. Both are sent by Soupy on the seller's behalf, name the seller and give its payment-profile contact email. Messages queued before this design keep their original plain body.


Bookable experience gifts
Choose New voucher → Gift type → Bookable experience. Select a published Bookings activity and activity-enabled portal, then set duration, guests, one fixed GBP price and optional Included on arrival extras. The activity must accept that duration and guest count. The gift belongs to the activity's venue. Save and publish are separate; each purchase freezes its package and original payment evidence. Money vouchers retain partial balances and all-venue options.
The recipient's private gift page shows the package and available start times. Book my experience creates one confirmed reservation and redeems the whole gift in the same transaction, with £0 further payment. Retries and competing tabs cannot reserve twice. Bookings' current opening hours, resources, buffers and capacity still apply; a failed reservation leaves the gift available. A newer public activity price does not change the package already purchased. An activity or portal withdrawn from sale is unavailable online; contact the venue.
Move to another date updates the same booking within the activity's change
policy and the venue's online-move setting. The original time stays reserved
until the replacement succeeds. Cancellation keeps the gift redeemed. In
Issued vouchers, staff with voucher correction and booking management access
may cancel an unstarted experience; staff with vouchers.correct may then
restore its recorded redemption with a reason. Restoration requires that exact
booking to be cancelled. Completed/started service cannot be silently reset.
The web Bookings running order labels the reservation Prepaid gift. Prepared native running-order source uses the same label; installed apps require a separate native build and acceptance. Its displayed value is a reference to the original gift; no second Order or payment is created. It cannot be invoiced again or spent as monetary voucher value. Refunds of an unbooked experience are whole-gift only; a booked gift must first be cancelled and restored before its original payment can be refunded.
This web implementation supports one activity at one venue. Practice reservations, location-first portals and additional card-guarantee flows are not available; dates covered by a scheduled card guarantee cannot be booked or chosen for a move. Included-on-arrival extras are frozen venue instructions; they do not reserve stock or create an add-on fulfilment claim. Native and live provider acceptance require separate evidence.

Purchase and customer voucher
Choose an amount, enter purchaser details and optionally name a gift recipient. Accept the displayed terms, then continue to the shared secure card form. The purchase page loads the card form on its own; reloading reuses the order's one payment. If loading fails, the page shows why and offers Load secure card payment to try again. Spendable value is issued exactly once only after verified provider confirmation. The browser’s payment result alone cannot issue value. Changed terms, unavailable sales or invalid payment setup prevent another charge. Unknown outcomes resume the same purchase and payment identity. Pending purchase pages automatically recheck confirmation for up to two minutes, without starting another payment. Checks pause while the tab is hidden or offline and stop on a terminal result or when leaving the page. If confirmation takes longer, the page keeps an explicit status check and explains that customers should not pay twice.
The purchaser and optional distinct gift recipient receive separately governed transactional messages containing the issued code, terms and a private voucher link. Delivery eligibility is checked again before dispatch; queued is not proof of delivery. The private link keeps its secret in the fragment and returns the voucher card, personal gift message, purchaser's name, issuing seller, permitted venue names, value, balance, status and terms, without purchaser or recipient contact details. The recipient can unwrap a designed gift card, which says who the gift is from by the purchaser's name, copy the code, refresh its balance or print a compact keepsake. Reduced-motion preferences suppress the opening animation; printing includes the card even before it is unwrapped. When a money voucher’s balance falls below its original value, the card shows the original value crossed out beside the remaining balance, including at zero. New codes use four groups of four characters, excluding I/O/0/1, with 80 random bits. Copy/paste, lowercase entry and spaces between groups are accepted. Existing GIFT-prefixed codes and private links remain valid.

BrewFerment website and customer accounts — prepared web
The prepared BrewFerment integration embeds its saved catalogue at /vouchers
with a curated theme=brewferment preset: cream background, ink text, brick accents
and BrewFerment typography. The public theme and origin-checked height messages
continue through purchase confirmation and the holder card. The preset changes
presentation; seller, terms, value, payment verification and redemption authority
still come from the voucher source.
BrewFerment customers use their existing loyalty email-link login at
/me/vouchers. Add your voucher explicitly claims an issued, live stored-value
voucher using its private email link. Buyer/recipient email matching never grants
ownership or consent. One purchase can belong to one external account; adding it
again to that account is harmless. The original private link remains valid.
The account displays current Soupy balance, expiry, status, code and terms, with
20 links per page and explicit refresh. No second balance ledger or loyalty
points conversion is created. Experience vouchers are outside this account slice.
The server connection is pinned to one business and embed and uses a dedicated signed credential. Missing configuration leaves account linking unavailable. Existing holdings remain visible if catalogue sales are disabled or a product is removed. Invalid, unpaid, practice, foreign-business or already-claimed vouchers cannot be added. Staff permissions and redemption flows are unchanged.
Fictional BrewFerment voucher account at mobile width
16 November 2026: actual components with synthetic responses, no customer data or payments. This is saved development source, not production acceptance. Both apps require deployment and protected configuration; real login, checkout, email and linked-account acceptance remain open. See the configuration and verification record.
Voucher QR and BrewFerment scanner — prepared web
Issued customer voucher cards now render their existing code as a local QR, including the printable card. The same readable code remains below it. Codes are never sent to a third-party QR service. Design previews carry no redemption QR; practice and unavailable voucher labels still apply. Existing issued codes work without reissuing value.
The prepared BrewFerment backend scanner accepts current grouped and older GIFT codes through camera, USB or manual entry. Scanning checks the current balance and venue; it does not spend value. Staff enter pounds and pence and an optional bill reference, choose Review redemption, then Confirm redemption. The screen shows the remaining balance. A £40 voucher used for £12.50 retains £27.50. The till still needs a matching voucher payment entry.
A separately configured staff connection pins the accepting Soupy venue and business. When configured to use BrewFerment's staff directory, any active BrewFerment backend account can use the scanner with their usual sign-in. The BrewFerment server rechecks their exact account for every lookup, confirmation and retry. Older staff sessions need one new sign-in. Soupy records the stable staff account on the redemption. No separate Soupy login is required. Integrations that use explicit Soupy staff mappings continue to check those permissions. The customer account connection cannot redeem vouchers. The shared voucher command retains venue scope, live and practice separation, refunds, expiry, balance revision and exact retry identity. Experience gifts cannot be spent as money through this scanner. No contact details are returned to the scanner.
An unknown response keeps the saved pending command in that browser tab; Retry same redemption reuses its identity. Reloading does not send a money command. A manager must resolve a pending result before starting another redemption in that tab. Browser offline caching is disabled for these scanner routes.
Mobile voucher QR preview and staff confirmation preview use fictional data. This is prepared source, not production availability. Protected connection settings, staff authority, coordinated deployment and real camera/USB acceptance remain required. See the validation and setup record.
Orders and sales by voucher
Overview shows Value sold, Value redeemed and Outstanding value, then Sales by voucher: each voucher product's number sold, value sold, value redeemed and outstanding value, largest sales first. A Refunded column appears once any voucher has a refund. Figures follow the Live vouchers / Practice vouchers switch and update as vouchers are sold, used, corrected or refunded.
Orders lists voucher purchases newest first, 25 at a time. Each row shows when it was ordered, the voucher, the purchaser's name and email, any gift recipient, the amount and any refund, the status, and the issued code with its remaining balance. Show chooses Purchases (paid, refunded or needing review), Unpaid checkouts (awaiting payment or never completed) or All orders.
Both need vouchers.customers.view, like Issued vouchers; product managers
without it see neither. For a business with vouchers sold before per-voucher
totals existed, the breakdown is summed from its vouchers, up to 200. Beyond
that, Overview says the breakdown is not available yet until a one-off support
rebuild runs. Business totals are unaffected either way.
Customer log, redemption and corrections
Issued vouchers searches code, purchaser and recipient in the current business, with pages of 20 records. Open a record to review contact snapshots, original value, remaining balance and paginated history. Redeem offers exact-code lookup. Enter the amount used and the redeeming venue, with an optional bill reference. Review redemption displays the amount and resulting balance; Confirm redemption applies it. A £100 voucher used for £35 keeps £65 available. Only a zero balance is fully redeemed. An expired, suspended, refunded or exhausted voucher cannot be spent. The server rejects stale balances, duplicate operation changes, excess amounts and venues outside its recorded scope.
Each use records staff attribution, venue, time, amount and balance. Authorised managers can reverse an exact recorded redemption with a reason. Repeated confirmation cannot restore value twice; the original entry remains. Staff must also record the voucher payment against the bill in the till; automatic till redemption is outside this web slice.
Overview reads maintained totals for value sold, redeemed and outstanding, rather than scanning customer histories. Live vouchers and Practice vouchers keep their lists, balances and redemption commands separate. Test-funded value cannot enter a live command. Practice messages do not dispatch through live email.
Refunds use the original shared Order and seller. Claiming a refund fences redemption before provider work; only unspent value is available for an operator refund. External refunds remain recorded even if they conflict with spent value, and suspend that voucher for reconciliation. A pending or failed refund is not proof money returned. A definitive provider failure/cancellation, or the canonical executor’s proof that it never contacted the provider, releases only that refund hold. A suspended voucher requires an explicit reviewed financial reconciliation; this first slice has no general-purpose balance editor.
Access and verification boundary
| Capability | Authority |
|---|---|
vouchers.view | Read product records. |
vouchers.manage | Edit/publish products and manage saved embeds. |
vouchers.customers.view | Read issued customer records, history and value totals. |
vouchers.redeem | Lookup and redeem current-business vouchers. |
vouchers.correct | Reverse a recorded redemption with a reason. |
vouchers.settings.view / vouchers.settings.manage | Module settings access. |
When a business enables Vouchers and no current administrator can delegate product access, a deployment administrator can review first Voucher product access for one existing business administrator. This grants viewing, creating and publishing products and managing their saved embeds for that business. It carries no delegation, customer, redemption, correction or settings authority.
A separate first redemption review for a recorded owner can add Redeem voucher value for the existing owner in one business. It requires current administrator authority and an intact product-access receipt. The permission cannot be delegated. The BrewFerment scanner still requires its own staff mapping and uses only the configured venue.
The owner full-access procedure gives the recorded Group owner all seven Voucher permissions with delegation, except any removed earlier, so they can grant Voucher access to staff in People & access. Earlier product and redemption grants stay in place; the owner does not need those procedures afterwards.
New legacy Vouchers viewer responsibilities include product viewing. New administrator responsibilities add product and Voucher settings management. Customer records, redemption, corrections and shared refund authority remain separately granted; existing immutable responsibility records are not rewritten.
Financial Order actions retain shared commerce refund and source authority. Vouchers grants neither Ticketing admission nor Loyalty rewards. Current module entitlement and source permissions apply; enabling a new entitlement cannot revive old pending purchases. This is web-only: Apple/Google Wallet, native apps, offline redemption, cross-seller settlement and online voucher spending in other checkouts remain outside this slice. The isolated development runtime blocks provider actions and delivery; local tests cannot certify Stripe checkout, received email or production availability.
Screens: /app/{orgSlug}/vouchers (Overview, Orders, Products, Issued vouchers,
Redeem, Embeds), /app/{orgSlug}/vouchers/settings, /embed/vouchers/{publicId},
/vouchers/purchase/{purchaseId} and /vouchers/view/{purchaseId}.
