Stripe Loyalty Integration: Turn Stripe Payments into Wallet Card Rewards
A Stripe loyalty integration turns a successful Stripe payment into a stamp, points or cashback on a customer’s wallet card. It works through webhooks and the API on the Business plan. This page explains how, and where Stripe Terminal fits.
Via API and webhooks, Business plan
Connect Stripe payments to the card
- Payment succeeds
- Stripe sends a webhook
- Relay matches the customer
- Card action runs
Handle refunds the same way, in reverse.
What does a Stripe loyalty integration do?
It makes a payment you have already taken in Stripe count towards a reward on a MSTRMND wallet card. Stripe tells your system that a payment succeeded, and a short piece of automation turns that message into an action on the card, such as adding the purchase amount for cashback or adding a visit.
There are two separate connections between Stripe and MSTRMND, and they are easy to confuse. Stripe bills your MSTRMND subscription. That is Stripe doing its everyday job and needs nothing from you. Your own Stripe payments can reward your customers. That second one is the integration this page is about. New to wallet cards? Start with our guide to digital loyalty cards.
How the Stripe connection works
Stripe can send a webhook, a message to an address you choose, whenever a payment succeeds. The Business plan includes API and webhooks, so a developer or an automation tool can receive that message and tell MSTRMND what to do. The flow has four parts:
- A payment succeeds in Stripe, online or in person.
- Stripe sends a webhook to a small relay: a developer’s code, or an automation platform such as Zapier or Make.
- The relay finds the customer by email or phone and matches them to a card.
- The relay calls the MSTRMND API to add a purchase amount, a stamp or a visit.
The MSTRMND API includes actions to create a customer, issue a card and add or subtract a purchase, a stamp, points or a visit. That is enough to model most reward rules, and enough to reverse them when a refund is issued.
Stripe and MSTRMND: the two connections
One is automatic. The other you build.
| Connection | What it does | Plan needed | Effort |
|---|---|---|---|
| Stripe bills your subscription | Collects your MSTRMND plan payment | Every plan | None |
| Webhooks and API from your Stripe | Turns a payment or refund into a card action | Business | Needs a developer or automation tool |
| Stripe Terminal | In-person hardware linked to the card | Not announced | Planned for Q4, no firm date |
Where Stripe Terminal fits
Stripe Terminal is Stripe’s in-person payment hardware. MSTRMND lists Stripe Terminal on its roadmap for Q4, with no firm date. Until it ships, in-person Stripe payments can still earn rewards through the same webhook route, because Stripe sends the same kind of event whether the payment was online or at a counter.
The practical difference is the matching step. Online, you usually have an email address. In person, you may have nothing to match on unless the customer has joined the card. A QR code at the counter that gets the customer onto the card before payment solves it.
Three ways to use it
Online sales with cashback
A shop that sells online and in person can give cashback on web orders, credited to the same wallet card the customer shows in the shop. The balance builds across both channels, which is the point.
Subscriptions and memberships
If you charge a recurring fee through Stripe, the wallet card can be a subscription or membership card that reflects it. The API includes membership tiers and renewal-date actions, so a payment can keep the card current.
Refunds that reverse the reward
A refund should not leave a customer with cashback for money they got back. The API includes subtract actions, so a Stripe refund event can reverse the reward on the card. This is the detail that separates a tidy setup from a leaky one.
Actions the API can take on a card
A Stripe event can trigger any of these. The list below counts the groups of actions in the MSTRMND API.
Bars compare the number of actions, not their importance. Source: MSTRMND API reference.
What you need before you start
- The Business plan, which includes API and webhooks.
- A Stripe account with webhooks enabled for the events you care about.
- Someone to build the relay: a developer, or a no-code tool such as Zapier or Make.
- A way to match a payment to a customer: email, phone or a card identifier.
- A written reward rule, including what happens on a refund.
What the Stripe link will not do
It does not replace a point-of-sale system, and it does not create customers who never join the card. It also needs setup. This is a good fit for shops with a clear rule and a developer or a patient owner, and a poor fit for anyone hoping for a button labelled “connect”. If that is you, the Scanner App on any plan is the fastest way to start.
Start with one payment type
The simplest Stripe loyalty integration rewards one kind of payment and ignores the rest. Choose the payment that matters most to you, such as a product page or a single price, and build the connection for that first.
Stripe sends many kinds of event, and a relay that reacts to all of them will reward things you never meant to reward. A narrow rule is easier to test, easier to explain to staff and easier to reverse. When it works, add the next payment type. A Stripe loyalty integration that grows one rule at a time is far easier to trust than one that launches with ten.
Frequently asked questions
Is Stripe already connected to MSTRMND?
In one way, yes: Stripe collects your MSTRMND subscription payment. Connecting your own Stripe payments to reward customers is a separate setup that uses webhooks and the API on the Business plan. It is not automatic, and it needs a developer or an automation tool to relay the events.
Does it work for in-person Stripe payments?
Stripe sends the same kind of payment event for in-person payments, so the webhook route can reward them. Stripe Terminal as a native link is planned for Q4 with no firm date. The practical challenge is matching a counter payment to a customer, which a QR code that gets them onto the card first can solve.
Can a refund remove the reward?
Yes. The API has subtract actions that mirror each add action, so a refund event from Stripe can reduce the amount, purchase, stamp or points on the card. Include the refund rule in your written reward rule before you build, because retrofitting it is harder than planning it.
Do I need a developer?
Not always. A no-code automation tool such as Zapier or Make can receive a Stripe webhook and call the MSTRMND API, which suits simple rules. A developer helps when you need matching logic, refunds or several reward types. If you want to start before any setup, the Scanner App works on every plan.
Key takeaways
- A Stripe loyalty integration uses webhooks and the API, both on the Business plan.
- Stripe already bills your MSTRMND subscription. Rewarding your own customers is a separate setup.
- Stripe Terminal as a native link is planned for Q4, with no firm date.
- Plan the refund rule first. The API can subtract as well as add.
- The Scanner App on any plan is the fastest way to start with no setup.