No app release needed
Journey builder Change the journey, not the app.
Choose the checks, their order and what happens when one fails, for each market. Change it any time, with no app release.
Pick the steps
Choose the checks a journey runs, and their order.
Set a fallback
Say what runs when a step can’t finish, such as video KYC after eKYC.
Per market
Each market keeps its own policy, limits and cool-offs.
No app release
Publish a change and the journey updates in your app.
Set what happens at each moment.
Pick a moment, write when a rule applies, and what it does. Try it: switch moments, change a condition, add one, drag to reorder, or change the action. The line underneath reads your rule back.
Actions
Reads assim.moved is true or behaviour.drift is true → step_up: face check, for 12 hours, show rebind_limit
Change it without a release.
Every journey is a map of blocks your team can edit. Run a new version in shadow first, publish it when it agrees with your outcomes, and every old version stays.
Version history
Version 15Shadow
Warn the customer when a payment starts during a call. Deciding on live traffic, not acting yet.
by Fraud operations
Version 14Live
Coached payments go to the call-back queue. New phones limited for 12 hours, not 24.
by Fraud operations
Version 13Replaced
Coached payments go to fraud review.
by Risk policy
Version 12Replaced
Kept with every decision it made, for audit.
by Risk policy
Show what applied, and when.
Every run is logged step by step, with the fallback that ran and the version that applied. A disputed case is answered with exactly what happened that day.
10:42•••
Open your account
1234
Full name
Priya Sharma
Mobile number
+91 98765 43210
- eKYCFailed
- Video KYCFallback, passed
- DocumentPAN matched
- FaceFACE_MATCHED
- DecisionAllow · v14
Questions banks ask.
Can our team change a journey without a release?
Yes. Journeys, fallbacks, policies and thresholds change in the builder and apply without an app release.
Can a journey differ by market?
Yes. Policies and thresholds are set and versioned per market, so a Singapore journey and an Indian one can carry different cool-offs and limits on the same SDK.
Can we show an auditor what applied to a decision?
Yes. Every run is logged with the journey version, the steps that ran, the decision and its reasons, so a disputed transaction can be answered with the record of what applied that day.
Try one-tap login on your own number.
See the network confirm your number with nothing to type, and the next check take over when it can’t. Then plan a shadow proof on one journey, measured on your own traffic.