Series 3 — Solution · Paper 10
A Network
Laura enrolled with her payment provider eighteen months ago. A bookshop she liked had started accepting payments through it and the setup took about four minutes — her name, her bank details, a confirmation from her bank that she was who she said she was. She has used it since then without thinking about it much. It works the way she expects it to work.
On a Saturday in March she is at a farmers’ market in a town she doesn’t know well. She buys a jar of honey from a stall she hasn’t visited before, points her phone at the card on the counter, and approves the payment. Her phone shows her a receipt. The honey seller’s phone buzzes.
Nothing about this feels different from any other payment she has made through the scheme.
What happened underneath was different from every payment she has made through the scheme.
The honey seller does not use the same payment provider as Laura. She uses a different one — a small operator that was set up eighteen months ago to serve independent food producers in the county, built on the same open protocol, operating under the same scheme rules, connected to the same trust infrastructure.
When Laura pointed her phone at the card, the payment request that appeared on her screen had been created by the honey seller’s provider. Laura’s provider — the one she enrolled with at the bookshop — received the request, recognised that it originated from a different operator, and handled the coordination automatically. It verified that the honey seller’s provider was a current member of the scheme, checked the trust certificates that confirmed the request was genuine, and presented Laura with the payment screen she recognises from every other transaction.
When Laura approved the payment, her provider instructed her bank to transfer the money to the honey seller’s account. The honey seller’s provider received confirmation that the payment had settled. Both providers updated their records. Both Laura and the honey seller received their receipts.
The two operators had never interacted before this transaction. They will interact again every time a customer of one pays a merchant of the other, automatically, without any configuration required from either operator or either user.
Laura did not know any of this happened. She did not need to. The payment worked the same way it always works, at a stall she had never visited, with a provider she had never heard of, in a town she doesn’t know well.
This is what a network looks like from the inside. Not a single system that everyone uses, but many systems that work together — each operated independently, each competing on the quality of what it offers, each connected to the others by a shared protocol that makes the boundaries between them invisible to the people on either side.
The honey seller’s provider has sixty-three merchants. Most of them are food producers, market traders, and small rural businesses — exactly the merchants the operator set out to serve. None of them could have justified the overhead of building their own payment infrastructure. All of them benefit from being connected, through their provider, to every payer enrolled with every other provider on the scheme.
Laura is one of those payers. She enrolled for a bookshop in a city. She paid for honey at a market in a different county. The two transactions are connected by nothing except the protocol that both operators built on.
The honey seller handed Laura the jar. Laura said thank you. Neither of them mentioned payments again.