Journeys
Pick by what you are doing today
The 4 journeys are not chapters and they are not sizes. Each cuts the platform on a different axis — product line, operational function, capability module, the event that starts it — and most banks live in 02 from launch onwards. 18 sections, 58 steps in all; 10 steps reach something the platform does not expose yet, and they are marked where they occur.
01 · split by product line
Launching a new card
From an empty portfolio to live, transacting cards. Pick your product line — the platform pattern is the same: authenticate, configure, issue, activate, transact.
You do this once per product line.
Credit66 steps, 2 of them hit a gap
Debit44 steps, 1 of them hit a gap
Prepaid55 steps, 3 of them hit a gap
02 · split by operational function
Managing a card
Everything after launch: limits, customer self-service controls, lifecycle events, day-to-day money movement, billing and disputes.
Where a live programme spends its time.
Limits22 steps
Controls & restrictions22 steps
Card lifecycle33 steps
Transactions & history44 steps
Statements & repayment22 steps
Disputes22 steps
03 · split by capability module
Enabling additional capabilities
Grow the program: installment propositions (EPP / IPP / BNPL), rewards, virtual cards and real-time events. Each capability switches on per product without re-platforming.
Switched on per product, as the programme grows.
EPP / IPP / BNPL — Credit44 steps
EPP / IPP / BNPL — Debit22 steps, 1 of them hit a gap
Rewards & loyalty22 steps, 2 of them hit a gap
Real-time events11 steps, 1 of them hit a gap
04 · split by the event that starts it
Handling an incident
The events a live programme reacts to: a card lost, a card expiring, a PIN blocked, a limit that has to come down, a card handed over the counter. Each one crosses several of the areas journey 02 lists, which is why it has its own path.
Reach for this when something has happened, rather than when you are building.
Lost or stolen card55 steps
Card renewal at expiry33 steps
PIN blocked, and unblocking it44 steps
Bringing a customer limit down44 steps
Handing over a no-name card33 steps
10 steps hit a gap
They call something the platform does not expose today: loading a prepaid balance, reward balances and movements, event subscription, and reading product parameters. Each is marked where it occurs, with the same mark on the step itself inside the journey.
A gap is an answer, not a defect — it tells you what to scope around before you commit. This portal does not state what its data cannot support.