Portal Home
The entry point for every audience, showing where every application sits right now.
One portal for the whole retail credit lifecycle. A customer applies from their phone in about ten minutes, AI-OCR fills the form from their documents, and a live rules engine scores and routes the file through to a card in the courier’s hands.
White-label · configured to your own policy, products and authority matrix
Retail banks running credit card and personal loan origination across sales, verification, credit and card operations.
The applicant photographs their documents on a phone. AI-OCR fills the form; they confirm rather than type.
A live rules engine scores each file against your current credit policy and routes anything outside it to the right approver.
A card in the courier’s hands, with every stage, query and approval on one auditable file.
Each stage is owned by a named role, and a file sits in exactly one at a time. The stage a file is in is the same fact the applicant sees, the queue counts, and the pipeline board reports.
Customer channels, back office, credit decisioning, fulfilment and management. Every area reads and writes the same file, so nothing has to be reconciled between them afterwards.
The entry point for every audience, showing where every application sits right now.
The applicant journey: OTP, product choice, upload-first onboarding and a digital form.
The same journey shaped for personal lending, with its own product rules and documents.
Where the file stands, and any query raised against it, answered by re-upload from the phone.
A queue per role, badged with what is waiting, so nobody hunts for their own work.
One application file: documents, extracted fields, history, and every action taken on it.
The decisions available to this role at this stage, and nothing that is not.
Identity, document and bureau checks, run centrally and recorded on the file.
Scoring, bureau pull and debt-burden ratio, computed live against the current policy.
Policy breaches routed by authority level, each needing the right signature to clear.
Embossing, personalisation, PIN handling and dispatch to the courier.
The whole book by stage and by vintage, plus a scorecard playground for policy changes.
The slowest part of a credit application has always been typing what is already printed on a document the applicant is holding. Upload-first onboarding inverts that: photograph, extract, confirm.
Mobile number and OTP, the product, then the camera. AI-OCR reads each document and reports which fields it filled, so the applicant checks rather than types.
The applicant photographs their identity and supporting documents and takes a live selfie. AI-OCR reads them and fills the form, so what is left is confirmation rather than data entry.
Mobile sign-up, product choice and documents, then only the sections that genuinely need a human answer, in short guided steps.
The same file can be opened by the customer themselves or by a sales executive sitting with them, and the portal records which channel every file came through.
When an analyst raises a query, the applicant is notified on the channel they came in on and can re-upload against that specific query: no branch visit, no restart.
The portal home opens the customer journey, every staff workspace and the management views, and shows where every application sits right now. A workspace tile is badged with the files waiting on it.
A live count of files at each stage with declines called out, then one tile per staff role badged with what is waiting on it. Nobody hunts for their own work.
A straight-through file, a query loop, a policy exception and a policy stop, each openable at the moment it matters, as the role that owns it.
Documents uploaded, AI-OCR fills the form, score 98, all the way to card dispatch.
An assisted file with the credit analyst. Raise a query, the customer re-uploads, the approver clears it.
Debt burden over benchmark. Routed to the authority that can clear that specific breach.
Waiting at central verification. A check fails policy, the file declines, and the reason is written to it.
From sales and relationship managers through verification, credit analysis and approval to card operations, each role sees exactly the files waiting on it.
Documents beside the fields they produced, the history of every stage it has passed, every query raised and answered, and the identity of whoever moved it, on one screen.
The action panel offers what this role may do at this stage and nothing else. An approval nobody has authority for is not a rejected click. It is not there.
Identity, document and bureau checks run centrally, early in the file’s life. Where your policy says a file cannot proceed, it stops there, and the reason is recorded on the file.
The scorecard, the bureau pull and the debt-burden ratio run against current policy while the file is still moving. A breach is routed to the level that can clear it, with the size of the breach stated on the approval.
Score, debt burden and bureau status on one panel, each shown against your policy, so a marginal file is visibly marginal rather than merely passing.
The scorecard, the bureau pull and the debt-burden ratio run against the live policy as the file moves, so a decision is never made against a snapshot from a week ago.
A file over benchmark is not simply declined. It is routed to the authority level that can approve that specific breach, with the breach and its size stated on the approval.
Policy changes can be modelled against the existing book before they are published, so the effect of moving a cut-off is a number, not an argument.
Products, document sets, scorecards, benchmarks and the authority matrix are all configuration. The integrations are the points where it meets what you already run.
We will run your own product and policy through every stage (straight-through, a query loop, and a policy exception) so you can see where your book would actually go.