Your rules become pass or fail steps.
Each step is pass or fail, so your team only acts when judgement is needed. The applicant completes the application: one question at a time, everything up front. Every action is on a timeline.
How an application starts
Two ways to start
The applicant completes the application in a guided flow. There are two ways to start it.
A public link starts the application.
The public link starts from a button on your website.
The applicant answers one question at a time. Fields appear only when needed. Everything is collected up front. You do not go back to the applicant later.
This link never changes, and multiple channels can use it.
You receive completed applications from vendors, dealers, and agents.
They call the API. We send a link to the applicant. The applicant completes the application. You receive it complete. No full integration needed.
The request contains:
- the region
- the asset list
- optional applicant information
We generate a unique link for that deal. The applicant provides the rest, one question at a time, with everything up front.
A branded application per programme
Each programme can have its own branded application for different products or countries. They land in that region's operational backend.
What runs
What the workflow contains
A workflow is the pass and fail steps from start to booking, so your team only acts when judgement is needed.
Applicant-facing steps
- the applicant completes the application
- dynamic question logic
- document uploads
- real-time validations
- identity verification entry point
- pre-filled data from public registers
- interest rates shown as they apply today
Platform automation
- data validation
- completeness checks
- rule evaluation
- credit logic
- KYC, AML, and sanctions checks
- collateral logic
- pricing and margin calculation
- risk-based adjustments
- vendor subsidy logic
- interest between start and deduction
- document generation
- amortization schedule creation
- routing when judgement is needed
- documents for signing
- reminders
- notifications
Case handler tasks
Only when judgement is needed:
- complete assigned task
- review flagged items
- perform four-eyes checks
- approve or decline what needs a person
- request additional documents
Signer steps
- authenticate
- sign the documents
Post-signing automation
- reservation logic
- advance logic
- payout logic
- notifications
- issue purchase order
- contract activation
- collateral logic
- sync with core systems
- auto-booking
- initialize acceptance procedure
- generating audit trail
- archive
When a handler sees the case
Your team only acts when judgement is needed
A handler sees a case when judgement is needed, for example:
- unclear or inconsistent documents
- identity mismatch
- sanctions match above threshold
- unusual credit result
- any condition defined by your rules requiring a decision
Those cases stay with a person until the step is decided.
How the steps decide
Pass or fail on every step
Pass or fail logic everywhere
Each rule returns pass or fail. If the system cannot decide, a handler sees that step.
Hybrid document validation
Uploaded documents vary in structure and quality. Machine learning extracts data when it can, and a handler confirms when it cannot.
Programme-specific rules inside the workflow
Each programme can have its own rules, documents, validations, and logic. Rules live in the operational workflow, not in a separate spreadsheet.
How a flow is started
Workflows can be triggered by public links, the One-Call API for specific flows, partner systems, or internal tools. They start differently. They land in that region's backend.
Who does what
What changes for each person
Case handlers
- only when judgement is needed
- no pile of incomplete applications
- work from the timeline
- four-eyes only when required
Management
- every action on a timeline
- rules live in the workflow
- start with one programme
- sits in front of your existing systems
Applicants
- one question at a time
- everything up front
- in their own time
Several programmes
Each programme has its own rules. You still start with one.
You can run many programmes and regions. Each programme and region can have its own:
- rules & business logic
- documents
- identity requirements
- interest logic
- subsidy rules
They send the region. Regional rules sit behind that request.
