Journal · Templates · 7 November 2026 · 19:42 SAST · by Jeremy Rich

A test bank where the customers actually do things

When we provision a bank from a template we can ask for sample data, and for a long time that meant a few hundred customers with accounts and balances, sitting there. It looked fine in a demo, and it was no use at all for finding problems, because nobody in it ever did anything. Nobody missed a payment, lost a card or argued with a merchant about a refund. Real books go wrong in the less common paths, and a test bank that never walks down them will pass every time.

So in early November we gave the sample customers lives. We call it a storyboard.

One customer’s life, written down

A story is one customer’s life, written as a short list of beats. A beat falls due on a day, or so many days after something happens in the business, like a statement being issued. Each beat does something (opens the account, taps the card at a grocer, pays the minimum) or checks something (the payment came back, the arrears fee was charged), and quite often both.

The first storyboard is for the United Kingdom card issuer template, and it has sixteen stories in it. One cardholder pays in full every month and is no trouble to anybody. One pays the minimum, and five days after the statement their bank refuses the debit. One loses the card and needs it reissued. Four of them dispute a purchase, and the four disputes end four different ways. My favourite is the everyday spender, who taps the card twenty-one days running at the grocer, the garage, a web shop, a restaurant, a cash machine and a shop in Paris, and then spends £90,000 at a jeweller, which is there to see what the spending rules make of it.

The whole thing is one settings file in the template. Twelve card scenarios that used to be twelve manual setups became one file that anybody on the team can read.

It plays as the day closes

The stories run inside day-end. Each time the test bank closes a business day, every story that has a beat due plays it. When we provision a bank we backdate it three months and walk it forward to today, so by the time anybody logs in there are three months of statements, payments, returns and disputes behind every customer.

The part I care about most is that the stories go through the front door. Every act is a call to the same API a clerk’s screen uses, made as a seeded member of staff, with that person’s permissions. If the bank is set up so that a second person must approve a refund, then the story’s approver has to approve it, or the beat fails and says so. We could have written the data straight into the database and it would have been much quicker, and it would have proved nothing.

It earned its keep before it had even landed. Proving the returned-debit story end to end turned up a fault in the reference we put on outbound Bacs collections, which no amount of static sample data would ever have found. It also taught us that an API can match its published description perfectly and still be missing a step somebody needs to finish the job.

From one template to a family

The merchant acquiring template got a storyboard of its own two days later, with four merchants in it: a high-street grocer, an online fashion shop, a hotel group and a gaming company.

The corporate banking storyboard is designed and not yet built. The design is that we write one storyboard for the whole family of corporate templates, and each sibling keeps the stories it has the features for and drops the rest. Working through it on paper has already been useful, because it showed that pool interest on a corporate structure settled without writing a journal entry. That is the sort of thing you would much rather find in a design review than in a client’s month-end.

What we haven’t done yet

The microlender and retail bank templates don’t have storyboards yet, and they’re next. The acquiring storyboard ships switched off. And the full three-month walk on the card tenant has been proved on a short cycle only; we estimated it at thirty-five to forty minutes from another template’s numbers and still owe ourselves the real measurement.

Written by Jeremy Rich.