Wallet passes that update themselves
Interlink Wallet adds a pass with your branding to your customers' Apple Wallet or Google Wallet, then keeps it current from your own data - commission balances, bookings and memberships. Nobody installs an app or remembers a login.
Scan with your phone, or open it here, to add the demo pass to Apple Wallet or Google Wallet. Your phone opens the right one.
- Pending
- £31.00
- Next payout
- 1 Oct
- Referral code
- M365-NC21
- Updated
- Today, 08:15
This demo runs in the page. On a real pass, the same change reaches the customer's phone.
Three pass types, available now
Each type is a fixed layout. You decide which of your data goes in each field and how amounts and dates are shown. Event tickets, offers and loyalty cards are in development.
-
Balance
Commission, credit and account balances. The figure changes when your system records a new amount, and cleared payments can appear on the lock screen.
Fields: earned · pending · next payout · referral code -
Booking
Appointments, shoots and reservations. When a booking moves, the pass shows the new time, and a reminder appears the day before.
Fields: date and time · location · who it's with · reference -
Membership
Member number, tier and renewal date, with a code that can be scanned at a front desk. An upgrade shows on the pass as soon as it is recorded.
Fields: member number · tier · member since · renewal date
How a change reaches the phone
-
Your system
Sends one request when something changes
A sale clears, a booking moves or a member upgrades, and your system posts one authenticated event. Sending the same idempotency key twice has no further effect, so retries are safe.
-
Interlink Wallet
Works out which passes are affected
The event is matched to every pass it touches. Your field map decides what goes where, and amounts and dates are formatted the way you set them.
-
Your customer's phone
Shows the new version of the pass
Apple Wallet and Google Wallet collect the updated pass. Changes you mark as important also appear on the lock screen.
curl https://wallet.interlink.digital/v1/events \
-H "Authorization: Bearer iw_live_..." \
-H "Idempotency-Key: sale-20417" \
-H "Content-Type: application/json" \
-d '{
"holder_ref": "agent-17",
"template": "commission",
"type": "commission.cleared",
"data": {
"earned_pence": 224750,
"pending_pence": 3100
}
}'
# 202 Accepted - every pass for agent-17 updatesInterlink has built and run web platforms since 1996, starting with the LinkCentre directory. We built Interlink Wallet for our own businesses first - commission for our sales agents, bookings through Fetch and membership for LinkCentre - then opened it up to other organisations.
It's built and supported in the UK. If you book a demo, you'll speak to the people who wrote it.
How your data and keys are kept separate
Interlink Wallet holds keys and data for many organisations at once. Keeping them apart is enforced by the database itself as well as by the application code.
Read how we protect your data- Tenant isolation
- Every tenant table enforces row-level security in PostgreSQL. A query without a tenant context returns an error rather than another organisation's rows.
- Signing keys
- Each organisation's pass-signing keys are encrypted separately and decrypted only at the moment a pass is signed.
- Audit log
- Privileged actions are written to an append-only, hash-chained log, so any change to past entries can be detected.
- API keys
- Stored only as hashes, limited to the actions you allow, and revocable immediately.
- On the pass
- Only what the holder needs to see. No bank details, card numbers or personal documents.
One person, one sandbox
Opening an account asks for a certificate kept in this browser. The same person cannot take a second credit. A pass on a phone is separate, and it does not carry the certificate.
-
01
Keep a certificate in this browser
The sign-up page asks for it. If this browser has none, you can keep one here, or approve from a phone that already has one.
-
02
One credit for that person
The credit is tied to the person, not to the email address. A second attempt with the same certificate is refused.
-
03
Then the sandbox
The account starts with test passes, watermarked TEST, on your own team's phones. Live issuing waits until the brand is checked.
Pricing
From £49 a month for 1,000 active passes. Growth is £199 for 10,000. No set-up fee.
You pay for passes installed on a phone, not for ones nobody adds. Extra thousands are £20, £12 or £6 depending on the plan. See the plans.
Questions
Do my customers need to download an app?
No. Apple Wallet is built into every iPhone, and Google Wallet is available on Android phones. Your customer taps a link in an email, a text or your website, and the pass is added.
Does the pass hold money or payment details?
No. It shows figures from your own systems. Payments and payouts work exactly as they do now.
Where does the information on the pass come from?
From your systems, sent to our API. Your records stay the source of truth, and the pass shows what they say.
How quickly do passes update?
Usually within seconds of your system sending an event.
Is Google Wallet supported?
Yes. Passes work in Google Wallet on Android phones as well as in Apple Wallet on iPhones, and they update the same way.
Can we use our own Apple and Google accounts?
[ANSWER TO CONFIRM]
What does sign-up ask for?
A certificate kept in this browser, then the organisation details. One certificate can open one sandbox. The pass you later put on a phone is not that certificate.
Can people remove the pass?
Yes, the same way as any other card in their Wallet. Removing it has no effect on their account with you.
See a pass change on your own phone
In a demo we add a pass to Apple Wallet or Google Wallet, send it an update, and show how your own data would map to it.