I am terrible at carrying loyalty cards.
More accurately, I am perfectly capable of carrying them. I simply never have the correct one with me at the exact moment somebody asks for it.
Somewhere at home will be a little piece of plastic proving that I have loyally accumulated whatever points, stamps or discounts the system has decided I deserve. Unfortunately I am standing in the shop and the card is not, so apparently the benefit no longer exists.
I find this disproportionately annoying.
The first idea behind Music Kite Connect was therefore not especially grand.
Why do I need all these bloody cards?
If I already have a Music Kite account, why could one private credential not represent the things I am entitled to use?
That would have solved the loyalty-card problem.
Then, as tends to happen, the idea escaped.
Fifteen pints behind the bar
Years ago I used to run and host open-mic nights. Sometimes a venue would put an allowance behind the bar for the performers: £50, perhaps, or fifteen pints.
That immediately became somebody's administrative problem.
Who has played? Who is entitled to a drink? Who has already had one? Does the bar have the same count I do? Has somebody accidentally redeemed twice? Is the remaining number in my head remotely connected to reality?
Nothing catastrophic. It is a pub tab, not a central bank.
But I remember thinking how much cleaner it would be if each performer simply had a right they could redeem themselves.
The organiser issues the entitlement. The performer presents it at the bar. The bar gets the answer it needs. Once it is used, it is used.
Then the obvious question appears: if the same mechanism works for a performer drink, why would it only work for a performer drink?
That is where Connect started becoming something more useful than a digital loyalty card.
The pass is not the entitlement
The simplest way to think about Connect is that a Music Kite user has one Pass.
The Pass is not itself a backstage pass, loyalty card, drink token, festival wristband or VIP ticket.
It is the credential through which the system can answer the appropriate question about whatever rights have been attached to that person in that context.
At the front door of a venue, the question might be: is this person entitled to enter?
At a second checkpoint, it might be: are they entitled to this particular area?
At the bar: do they have this benefit available, and has it already been used?
At a festival: does this credential currently carry access to this site or zone?
Same Pass. Different question.
The important part is not the QR code or whatever happens to be displayed on the screen. The important part is the controlled set of rights behind it.
That distinction matters because static credentials are easy to confuse with the thing they represent. A plastic card feels like the entitlement itself. A screenshot of a barcode starts looking like the right.
Connect is intended to work the other way around.
The Pass stays the same. The rights behind it can change.
The person at the checkpoint should know as little as possible
Once I started thinking about access, the privacy side became much more interesting.
If somebody behind a bar needs to know whether I have a valid reward, they do not need my email address.
They do not need my phone number.
They probably do not need my name.
They need an answer appropriate to the checkpoint: valid, expired, already used, revoked, no uses remaining — whatever the rules of that entitlement require.
There are contexts where identity genuinely matters. A named, non-transferable ticket may require a different level of checking. Backstage access may have rules that a coffee loyalty reward does not.
That does not mean every person in the operational chain should get the same information.
This is a principle I increasingly like in software generally: reveal what the person needs to make the decision, not everything the system happens to know.
The member of staff checking entry does not need access to the wider Music Kite account. They need to know whether this credential is valid for this action now.
Enough information. No more.
Delegation should not mean losing control
The other side of the design is provenance and authority.
Imagine an organiser creates 1,000 event entitlements and allocates 250 to each of four managers to distribute.
The managers can perform the job they have been given without becoming the original issuer. The organiser still has a record of where the allocation came from, what has been distributed, what has been redeemed and what remains.
The issuer also controls the rules.
Can the benefit be transferred? Can somebody pass it on? Where can it be redeemed? How many times? When does it expire? Is it personal? Can it be revoked?
Delegation becomes a chain of authority rather than a point where ownership quietly disappears.
That may sound like a lot of machinery for a loyalty card.
It is.
It makes more sense when the same underlying mechanism can also represent entry, area access, performer benefits, festival entitlements or anything else where provenance and controlled redemption matter.
Revocation is where the real world arrives
A physical pass has an obvious weakness: once you hand it over, changing your mind can be difficult.
If somebody's access has to be revoked, you cannot rely on physically recovering every badge, wristband or screenshot already in circulation.
A credential whose rights are checked against the current system can behave differently. The visible Pass can stay the same while the entitlement behind it changes.
That is the attractive part.
The awkward part is that real venues and festivals have terrible connectivity at precisely the moments you would most like perfect synchronisation.
Offline use therefore cannot be treated as a magical promise that networking has ceased to matter. If a checkpoint and a credential are both genuinely disconnected, there is a limit to how quickly a new revocation can become known there.
The system can mitigate that with bounded offline authority, expiry and warnings, but it cannot negotiate with physics.
I like admitting that kind of limitation. It tends to produce better systems than pretending edge cases have been defeated by confidence.
Once the mechanism existed, the uses multiplied
This is the part where the original loyalty-card annoyance became almost incidental.
Artists can recognise attendance or issue supporter benefits. Venues can use the same underlying approach for access, re-entry, areas and loyalty. Festivals can use checkpoints across sites and zones. Vendors can redeem benefits without surrendering ownership of their own loyalty relationship simply because they happen to be trading inside somebody else's event.
Then you can start linking participation to other things. A Fan collects an eligible Gig card because they attended. A festival can create a challenge involving real places or participating vendors. An organiser can issue a benefit and know where it came from without turning the user into a bundle of personal information at every checkpoint.
The possibilities spread quickly.
That is useful and also exactly where I have to stop myself turning a simple user-facing concept into a manifesto about universal identity.
I do not need Connect to become the credential system for civilisation.
I need it to be useful in Music Kite.
The complicated part should disappear for the person using it
The funny thing is that the more complicated the system became underneath, the simpler I wanted the public idea to become.
One Pass. Many uses.
All of the difficult things — issuer authority, delegation, privacy, provenance, redemption, revocation and audit history — exist so the person holding the phone does not have to understand them.
That is generally the kind of technology I like most.
Complex underneath. Boringly obvious on the surface.
If somebody walks into a venue, presents their Music Kite Pass and the right thing happens, that is enough.
They do not need to know which entitlement was resolved, which issuer chain authorised it or how the scanner arrived at the answer.
They just need to trust that it works.
And, as a minor personal victory, perhaps I can finally stop pretending I will remember where I put the loyalty card.