Gift Cards and Marketing

These pages are organization-scoped and appear only when the corresponding feature is enabled. Gift Cards and Wallet Pass Branding use the gift-card feature; Marketing and Customer Display Ads use the marketing feature.

Navigation label	Read or page access	Additional change access
Gift Cards	store.gift_cards.read	store.gift_cards.write to issue; also org.admin to import or revoke
Marketing	org.marketing.read	org.marketing.write
Customer Display Ads	org.advertisements.read	org.advertisements.write
Wallet Pass Branding	org.settings.read	org.settings.write

If one of these pages is missing, ask an organization administrator to check both your permissions and the organization's enabled features.

Choose the right page

• Use Gift Cards for customer gift-card issuance, balances, status, imports, and revocation.
• Use Marketing for one-time customer campaigns and automated SMS messages based on customer or loyalty data.
• Use Customer Display Ads for image creatives delivered directly to customer-facing POS displays. These are not SMS or email campaigns.
• Use Wallet Pass Branding for the identity, images, and colors on gift-card passes saved to Apple or Google Wallet. It does not change POS, receipt, invoice, website, or legal branding.

Sell a gift card

Use Virtual Terminal > Giftcards with a selected store and both store.transactions.write and store.gift_cards.write.

1. Enter the Gift Card Amount.
2. Complete Recipient Details, optionally adding Gift Message (Optional) and From (Optional). This form does not select or link a customer.
3. Choose Email, Text Message, or Email & Text, supplying the corresponding recipient contact details.
4. Select In Person – Manual Card Entry or Phone Order – Card Not Present.
5. Review the amount in the bottom confirmation and select Sell Gift Card • $XX.XX to open the secure Peak Gateway payment form.
6. Complete the required fields in that form, then select Sell Gift Card • $XX.XX again to submit payment.

The form opens without validation styling. Inline feedback checks amount syntax; the server validates the $5 minimum and the contact details required for the selected delivery method before payment starts. Review any server rejection and correct the details before submitting again.

An incomplete secure payment form keeps the hosted entry open for correction. A hosted payment notification alone does not confirm the sale: PeakPOS checks the server's payment outcome and gift-card issuance status before showing the issued card. If payment completed but delivery could not be completed, do not charge again; use the displayed issuance reference when contacting support.

Activate a gift card sold at a terminal

A completed terminal sale creates a server-stored activation task for each sold gift card. Pending tasks do not block the next checkout and remain available after the terminal app restarts.

• Open the pending gift-card task list and select the card to activate. Scan the physical card, or provide the recipient details for virtual delivery. The task supplies the denomination and original funding sale; do not enter a replacement sale amount.
• Once issuance completes, select Retrieve issued card code to obtain the redeemable code for the customer. The scanned reference is not a substitute for the issued code. Virtual delivery uses the issued code.
• You can close the task list and continue serving customers while an accepted activation or delivery is pending.
• If virtual delivery has not completed, correct its unsent contact details with Update delivery contact. This keeps the same issued card; contacts that already received it cannot be changed.
• To reverse the funding sale, submit the reversal from its task. The server determines the permitted reversal from the stored transaction and validates issued-card usage, settlement, and any required approval. A request is not confirmation that the funds have been reversed.
• If the server asks for a cash handoff, return the displayed amount once and explicitly confirm that handoff. If cash has already been handed over, retry only its confirmation. If you are uncertain whether it was handed over, do not pay it again. Do not return cash merely because a reversal is pending.
• If the queue asks to renew authorization, complete that check on the existing reversal even when current policy no longer requires a manager PIN. Renewing authorization does not reset an acknowledged cash handoff.
• Bank-card and gift-card refunds advance independently. The sale remains pending until every required refund is complete; a pending bank refund does not prevent an independent gift-card refund.
• A historical sale whose original currency cannot be recovered is held for review. Activation stays unavailable; the terminal does not substitute today's store currency.
• On a receipt containing both goods and gift-card funding, goods-only returns remain available within the original goods balance. Returning goods does not revoke the funded card or make its funding refundable through an ordinary return.

Gift-card tender availability comes from the server's current usability response. Checking a balance does not reserve it; the server validates the card again when the tender is submitted.

Terminal SDK integrations must migrate the removed direct activation, virtual-send, and cash-return operations to the activation-task and funded-sale reversal APIs. The balance response now requires the server-owned usable field; balance or status alone is not tender authorization.

Issue and track Gift Cards

Gift cards are managed at the organization level by Peak Gateway. The list shows masked card digits only.

Find a card

1. Go to Organization > Gift Cards.
2. Choose Active or History.
3. Use Search gift cards to find a card by the visible masked code.
4. Review Balance, Status, Expires, and Created.

Active and History use the server's usability projection, including current status, balance and expiry at read time. The browser clock does not decide which cards are usable; refresh the list for the latest state.

Create a gift card

Issuing a single card requires store.gift_cards.write and a selected store so PeakPOS can use the correct Gateway location.

1. Select the store in the sidebar.
2. Go to Organization > Gift Cards.
3. Select Create Gift Card.
4. Enter an Initial Balance greater than zero and, if needed, Expires At.
5. Optionally add Recipient Email, Recipient Phone, Recipient Name, From (Optional), and Gift Message (Optional). Email or SMS delivery uses the contact fields you provide.
6. Select Create.

If Create Gift Card is disabled, confirm a store is selected. If the button is absent, ask for the store gift-card write permission.

Import or revoke cards

Users with both store.gift_cards.write and org.admin can:

• Select Import Existing Gift Cards, select Download Template, complete the CSV, and choose it under CSV File. Select Preview Import, review the masked preview and any row errors, and then select Confirm Import for the selected store.
• Select Revoke on an active card. Revoked cards move out of the active view and cannot be used as active tender.

Review the list after an import timeout before retrying; the Gateway may already have accepted the cards. Never include unneeded customer data in an import file.

If the page says Gateway location not connected, contact Peak Support. Gift cards become available after Support pairs and authorizes a store's Gateway location.

Build a one-time customer campaign

Recipient preview is consent-aware.

1. Go to Organization > Marketing.
2. Under One-time campaigns, enter a Campaign Name and choose the Channel.
3. Choose a Saved segment or build an inline audience. Inline rules can match All rules or Any rule.
4. Enter the Message Body and, when the field is displayed, provide an Email Subject.
5. Select Save Draft if the campaign is not ready.
6. Select Preview Recipients and review eligible and excluded recipients before delivery.
7. Either:
   • Choose a future Schedule for time and select Schedule, or
   • Select Queue Send, review the eligible-recipient count, and confirm Queue Send.

You can save an inline audience as a reusable segment. Scheduled campaigns can be cancelled before delivery. Campaign creation, segment changes, scheduling, sending, and cancellation require org.marketing.write; users with read access can review activity and saved campaign details.

Do not use campaign preview counts as a customer list export. SMS eligibility depends on active consent across the organization, as described on Settings > SMS Consent.

Configure automated messages

Automated messages are the second section of Marketing and are separate from one-time campaigns. Each one sends a text message (SMS) to the customer's phone on its own whenever the customer matches its rule, and only customers with SMS consent on file are messaged. The currently creatable types are:

• Points threshold: sends when a customer reaches the minimum loyalty points you set.
• Birthday: checks for customers with a birthday on file.

Older Win-back and First purchase rows can appear in the list and history as unavailable legacy types, but they cannot be newly created from this page.

1. In Marketing, find Automated messages.
2. Select Create automated message.
3. Choose the Sends when type.
4. For Points threshold, enter Minimum points greater than zero. Saving with a lower value shows an inline validation message instead of doing nothing.
5. Enter the Customer message. It is sent as SMS, and the supported variables shown in the form are {name} and {points}.
6. Set Status to Active or Paused. Paused messages keep their rule but never send.
7. Save the automated message.
8. The list shows each message's Sends when rule, so two messages of the same type are still distinguishable. Use Preview audience to check how many customers currently match (the result panel names the message it came from) and History to review sent messages and results.

Users with org.marketing.write can create, edit, pause, and delete supported automated messages. Read-only users see an explanation in the section instead of an unexplained disabled button. Deleting stops future messages and cannot be undone.

Publish Customer Display Ads

Customer display ads are direct merchant-controlled creatives for POS customer displays.

Create an ad

1. Go to Organization > Customer Display Ads.
2. Select New ad.
3. Enter Title and, optionally, Description.
4. Under Device preview (16:9), upload JPEG, PNG, GIF, or WebP artwork under 5 MB. A 1920 × 1080 image is recommended.
5. Choose Placement:
   • Idle display
   • Between transactions
   • Checkout display
6. The sidebar-selected store is preselected under Target stores. Choose the intended Target stores or Target store groups; with no target selected, the ad is eligible for every store in the organization.
7. Optionally set Start and End dates. To restrict delivery to daily hours, enter both Daily start (store local) and Daily end (store local); leave both blank for no daily-hour restriction.
8. Set Rotation order to a whole number from 0 through 1000 and choose whether the ad is Published.
9. Select Create ad.

Times use each target store's timezone. Published changes reach online terminals within five minutes. A higher rotation order is fetched first, but eligible creatives rotate evenly; the number is not an impression weight.

Maintain targeting and results

• Use Store groups to create reusable multi-location targets.
• Use All ads or Published to filter the creative list.
• Select Edit to change a creative.
• Select Archive to stop delivery while retaining impression history.
• Under Delivery analytics, filter by dates, store, and ad. Review verified device impressions and unique devices by store-local date and placement.

All users with org.advertisements.read can review ads and analytics. Creating, editing, archiving, uploading images, and changing store groups require org.advertisements.write.

Configure Wallet Pass Branding

Wallet pass branding controls what customers see when they save a gift card to a wallet.

1. Go to Organization > Wallet Pass Branding.
2. Under Wallet pass identity, enter the Display Name shown instead of the organization name.
3. Under Wallet pass images, upload:
   • Logo image for Apple and Google Wallet gift-card passes and emailed receipts.
   • Icon image for Apple Wallet gift-card passes.
4. Under Wallet pass colors, set valid hex colors for Background, Text, Primary, and Secondary / Labels.
5. Review the Gift card pass preview.
6. Select Save Wallet Pass Branding.

Uploaded image types are PNG, JPEG, GIF, or WebP. The upload service supplies the image URL used for pass generation. Users with read access can review the effective branding; org.settings.write is required to upload or save changes. When no custom record exists, the page clearly shows that default wallet pass branding is in use.