Skip to content
FinTech · Playbook

The fintech playbook. Built in the builder, decided by your ledger.

Ten journeys, each drawn below as it runs. The decision comes from your ledger, your credit engine or criteria you set; the journey carries it. Aims are targets to agree in the pilot, not results.

PLAYBOOKS · 01

Fund the wallet within forty-eight hours of KYC.

A verified wallet with no top-up after forty-eight hours gets one push that opens Add money, and one WhatsApp three days later if money still has not landed; the journey stops the moment it does.

Decides
your ledger's KYC and top-up events.
Aim
more wallets funded in the first week.
Built in the journey builder
Fund the wallet within forty-eight hours of KYCFINTECHStarts when your ledger says verified; stops the moment money lands.
FinTech
PLAYBOOKS · 02

Offer the savings pocket the day the salary lands.

A salary credit into the wallet asks your ledger whether the user already holds a pocket, then sends one WhatsApp with Open a pocket or Not now; a tap goes to your system to open it.

Decides
your product rules and what your ledger holds.
Aim
pockets opened without a campaign.
Built in the journey builder
Offer the savings pocket the day the salary landsFINTECHYour ledger confirms the pocket is not held before anything is offered.
FinTech
PLAYBOOKS · 03

Raise the limit the day the third instalment clears.

A third instalment paid on time asks your credit engine whether a higher limit is available, then sends one WhatsApp with Raise my limit or Keep it; a tap goes to your system to apply it.

Decides
your credit engine.
Aim
limits raised without a call, only where your engine agrees.
Built in the journey builder
Raise the limit the day the third instalment clearsFINTECHYour credit engine answers before anyone is offered anything.
FinTech
PLAYBOOKS · 04

Turn an unused credit limit into a first draw.

A limit approved and untouched for thirty days checks with your credit engine that it is still live, sends one Story on three ways to use it, and one WhatsApp with a use case if they read it.

Decides
your credit engine and your segment definition.
Aim
first draws on limits that were sitting idle.
Built in the journey builder
Turn an unused credit limit into a first drawFINTECHA check with your credit engine, then one Story, then a WhatsApp only if they read it.
FinTech
PLAYBOOKS · 05

Bring the Add money visit to a top-up.

A session with the Add money screen opened twice and no top-up sends one push that opens the step they left, and one WhatsApp with the same link if money has not landed by the next day.

Decides
a session rule you set.
Aim
more first top-ups from users who already tried.
Built in the journey builder
Bring the Add money visit to a top-upFINTECHA session rule, a consent check, one push to the step they left, one WhatsApp if nothing lands.
FinTech
PLAYBOOKS · 06

Catch the wallet that is emptying quietly.

A user whose top-ups have fallen on your RFM windows enters At Risk, gets one Story on the feature they never used and one nudge if they read it; if not, the journey waits and moves them to Lost with no more messages.

Decides
your RFM definitions.
Aim
the drifting user reached once, before the balance is gone.
Built in the journey builder
Catch the wallet that is emptying quietlyFINTECHOne Story, one nudge if they read it, then silence.
FinTech
PLAYBOOKS · 07

Set up autopay on the third bill to the same biller.

A payment event from the receipt you already send, the same biller for a third month, asks your ledger whether the biller is on file, then sends one WhatsApp with Set up autopay or Not now; a tap goes to your system to schedule it.

Decides
your ledger and the pattern you define.
Aim
bills that pay themselves, and a user who stays.
Built in the journey builder
Set up autopay on the third bill to the same billerFINTECHThe receipt you already send is the trigger; your ledger confirms the biller first.
FinTech
PLAYBOOKS · 08

Finish the KYC that stalled at the document.

A session that started KYC and ended with no document uploaded sends one WhatsApp with a tap to continue where they stopped, checks your ledger, and sends one SMS with the same link if they are still not verified.

Decides
a session rule you set; your ledger's KYC status.
Aim
more verifications completed.
Built in the journey builder
Finish the KYC that stalled at the documentFINTECHA session rule, a consent check, one WhatsApp, and one SMS if your ledger still says unverified.
FinTech
PLAYBOOKS · 09

Remind on the instalment date, then escalate.

The journey waits until the date your ledger holds, sends Pay now, stops when paid, and escalates by channel if not, with the outcome written back.

Decides
your due dates and risk tiers.
Aim
higher on-time repayment, lower cost to collect.
Built in the journey builder
Remind on the instalment date, then escalateFINTECHWaits until the date your ledger holds, stops when paid, escalates by channel if not.
FinTech
PLAYBOOKS · 10

Grow by referral, credited honestly.

A tap on a per-person link is matched to an install, deterministically on Android and as an estimate on iOS, and the sharer's reward waits for the new user's first payment before your system pays it.

Decides
your reward rule; your ledger's first payment.
Aim
member-get-member that pays for a paying user, not an install.
Built in the journey builder
Grow by referral, credited honestlyFINTECHThe reward waits for the new user's first payment, not the install.
FinTech

Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the model.

The pilot

One use case. Six to eight weeks. A number you agreed first.

Book a Demo