How to create your first stamp card in Waya

Decide three things before you open the designer

Building the card takes about ten minutes. What slows most owners down is opening the designer before they've decided three things: how many stamps, what the reward is, and what the card is called. Settle those on paper and the rest of setup is mostly typing.

Stamp count is the decision with real consequences. Waya accepts any number from 1 to 50 and defaults to 10, and the hint under the field says most cafés pick 8 to 10. That range is a compromise: low enough that a twice-a-week regular can see the finish line inside a month, high enough that the free item doesn't erase your margin.

The reward has to be one specific item. "Free coffee" works. "A discount on your order" doesn't, because your cashier will read it differently on a busy Thursday than you did when you typed it. If the reward needs a footnote to be understood, pick a different reward.

The card name matters more than people expect, because it isn't just an internal label. Waya prints it as the brand text at the top of the wallet pass and in the SHOP row, on both Apple Wallet and Google Wallet. Use the name customers say out loud. A card called "Loyalty Program 2026" sitting between someone's boarding pass and cinema ticket looks like something to delete.

Sign up, then walk the six setup screens

Start at /signup with an email and a password. No credit card, and nothing to install. New accounts drop straight into a six-screen setup flow, and no loyalty program is written to your account until the final screen, so you can go backwards through the middle screens without leaving half a card behind.

Screen 1 collects your shop details. Screen 2 is "Add your brand": upload a square logo, ideally a PNG around 512x512 px and under 2 MB. There's a checkbox to pull the card color out of your logo automatically, which saves you guessing at hex codes.

Screen 3 is "Build your card", where the actual work happens. Screen 4 is "Customize the join page" — the one screen a customer sees after scanning your QR code. Note that there's one join page per shop, shared by every card you ever make, so treat it as your storefront rather than as part of this card.

Screen 5 is "Add your branches". Screen 6 confirms the card is live and hands you "Add to Apple Wallet" and "Add to Google Wallet" buttons so you can test on your own phone. Two things Waya deliberately doesn't do at any point in this flow: it doesn't connect to your till or payment terminal, and it doesn't send SMS. Staff add stamps by scanning the customer's card on an ordinary phone.

Inside "Build your card": what each control does

The screen is numbered 1 through 6: Card type, Reward rule, Reward name, Card color, Stamp icon, and Banner. The preview beside it redraws as you type, and you can flip it between the Apple Wallet and Google Wallet renders. They are not identical. Check both before you decide the design is done.

Card type is where the free plan shows its edges. Stamp cards are available on 0 SAR; points, balance, and discount cards carry a "Paid plans" lock and need Growth at 85 SAR a month. For a first card this is rarely a problem, because a stamp card is the format customers already understand from paper.

Reward rule reads as a sentence you complete: "Buy 10, get 1 free." Reward name is what appears on the pass under the REWARD label, so keep it to two or three words. There's also a reward quantity field if a completed card should grant more than one item, which is how you build "2 free coffees every 8 visits" without doubling the stamp count.

Card color offers eight presets — Waya emerald, black, warm neutral, sapphire, ruby, amethyst, terracotta, and teal — plus any hex value and a separate text color. Stamp icon decides what fills each slot: numbers counting 1 to N, or a single repeated icon that fills in as stamps land. Numbers are easier for a customer to read at arm's length; icons look better in a photo.

Check the stamp math before you commit to a number

Under the reward rule there's a collapsed panel labelled "Will this be profitable? — quick check". It asks two numbers: what one item costs you, and what you sell it for. It's worth opening even if you think you know the answer, because the arithmetic includes the free item, which is the part people forget.

The formula is simple enough to do on paper. Revenue per completed card is the stamp count multiplied by your price. Cost per completed card is the stamp count plus one, multiplied by your cost — the plus one being the reward you give away.

Worked example, assumptions stated: a latte you sell for 15 SAR that costs you 5 SAR in beans, milk, and cup, on a 10-stamp card. Revenue per cycle is 150 SAR, cost is 55 SAR, so you keep 95 SAR per completed card. The effective discount to the customer is 3.3%, which is cheaper than almost any promotion you could run instead.

Now a tighter one: an 18 SAR sandwich that costs you 12 SAR to make, on a 3-stamp card. Revenue is 54 SAR, cost is 48 SAR, and you keep 6 SAR per cycle. Waya flags that as "Tight margin" and suggests at least 4 stamps. Both examples assume every stamp is a full-price sale of that same item and ignore rent and labor, so treat the output as a sanity check, not a forecast.

What to check before you print anything

Add the pass to your own phone first, from the "Add to Apple Wallet" and "Add to Google Wallet" buttons on the final screen. Then look at it as a stranger would: is the shop name readable, is the reward obvious, does the stamp row look right at 10 stamps and at 0? Most design mistakes are invisible in the editor and obvious on a lock screen.

Check the stamp count one last time, because changing it later changes the target for everyone already holding the card. The pass reads the stamp count from your program every time it refreshes, so raising 10 to 12 turns a customer sitting at 7 of 10 into 7 of 12. That is a conversation you don't want at the register.

Understand what the Address and Google Maps URL fields on the card actually do. They are back-of-pass information, shown when someone flips the pass over. They do not create a geofence. Lock-screen reminders when a customer is near your shop come from the Branches screen, and nowhere else, so filling in an address is not the same as setting up proximity notifications.

Write your terms while you're there. One line on the back of the pass — something like "One reward per visit. Non-transferable. Valid at participating branches." — settles most disputes before they start. Also set the pass language: Auto follows the customer's device, or you can pin the pass to English or Arabic.

Only then print. The posters tab generates print-ready sheets carrying your card's QR code; one by the register does more work than a stack of flyers. Free-plan ceilings to keep in mind: 100 customers, 100 wallet messages a month, 1 card, and 1 branch. When you cross 100 customers, enrollment stops, but everyone already enrolled keeps their card and keeps collecting stamps.

Editing the card after it's live

Once the wizard is done, the full designer lives on the Designer tab of your dashboard, and it exposes more than the six-screen flow did: Card Info, Card color, Images, Stamp icon, Content, and More info for the back of the pass. Every edit you save pushes out to passes already in customers' wallets, without them doing anything.

The designer keeps an undo and redo stack and autosaves a local draft, which is worth knowing because it means you can experiment on a live card and step back. If you leave with unsaved changes it will ask first, and it will offer to restore a recovered draft next time you open it.

Colors, logos, and reward wording are safe to revise at any point. The one field to change carefully is the stamp count, for the reason above. If your first card taught you that 10 stamps is wrong for your shop, the cleaner fix on a paid plan is to launch a second card at the number you want and let the first one wind down, rather than moving the goalposts on people mid-collection.