An agent live in ten minutes. Under your bank’s name.
Trustt Digital Distribution is an agency banking platform that lets a bank onboard business correspondents and DSAs and sell loans, deposits and cards through them under its own name.
One integration replaces every point-to-point partner build. BCs, DSAs and digital platforms distribute your whole shelf, under your entitlements, your audit trail, your name.
- IBA · NPCI · FactivaAdverse media · blacklistClear
- PAN validationName · DOB matchVerified
- CIBIL · PosidexBureau · de-dupe against your bookThreshold met
- Aadhaar eKYC + OTPOn the agent’s own deviceDone
To onboard a partner network
Agent self-onboarding
Distributable products
Buying distribution looks like buying reach.
Six partner networks means six contracts, six security reviews and six release cycles. DDP sits once between your core and all of them; every network after the first is configuration.
- Whose network, the operator’s agents and their next bank, or yours
- Whose customer, a partner in the middle, or your own relationship
- Whose obligation, you are the RBI principal, whoever’s software captured it
A banking outlet that fits on a counter.
Instead of a branch the economics can’t justify, the bank equips someone already there to act as the bank. What that counter can do today:
Bank as principal, at the counter
Running the network at scale
Application sourcing
Three jobs · one supervised perimeter from 1 Jan 2027
- Cash withdrawal & depositAePS · microATM
- Remittance & transfersIMPS · UPI · NEFT
- Account opening & depositsFull KYC · product master
- Loan origination & disbursalSame engine, every channel
- Card sourcing & issuanceCard policy · virtual issuance
- Government schemesPMJJBY · PMSBY · APY
- Bill payment & rechargesBharat Connect
Ten minutes, because nothing in it is waiting for a person.
Elsewhere onboarding is a queue, couriered forms, a Friday activation batch. Here every check is an API call, run concurrently the moment the agent registers.
Register
The partner shares a link. The agent opens the app and starts, no paperwork, no branch visit.
Eight checks
Adverse media and blacklists are a hard stop; bureau and de-dupe run against a threshold you set.
Go live
Aadhaar eKYC with OTP on the agent’s own device, then distributing, about ten minutes after the link arrived.
Suspends automatically
factiva_hitcibil_breachdormancy_90dEvery transition rule-stamped and retrievable by API, the record an inspector asks for.Individual BC to a managed DSA marketplace, one rail.
A village BC on a basic Android phone and a national DSA network on APIs are worlds apart. DDP fits the engagement mode to the partner.
One entrepreneur, one APK, live today.
A village-level entrepreneur on a basic Android phone. Registers from a link, clears the eight checks, transacts the same morning.
- EngagementAPK
- Time to liveSame day
- EntitlementPer-agent product subset
A multi-state company, entitled to your whole shelf.
Supervisors and agents in a hierarchy, each tier entitled from one manifest. The company brings the people; you keep the customer.
- EngagementAPK · SDK
- Time to live~1 week
- EntitlementFull shelf, by tier
Built around cards. Every lead deduped before a bureau pull.
A managed marketplace of DSAs sourcing card applications. Offer variant and limit come from your policy; the card is issued in the same session.
- EngagementAPI · portal
- Time to live~1 week
- DedupeYour book, pre-bureau
Marketplace, neobank or employer platform, on your APIs.
Self-serve or assisted journeys embedded in a partner’s product, decided by your rules engine, booked in your core.
- EngagementSDK · API
- Time to live~1 week
- JourneysSelf-serve · assisted
POST /v1/applications { "partner": "neo_01", "product": "savings_basic", "customer": { "kyc": "aadhaar_otp" } }201 Created · 412 ms{ "id": "AP_3391", "decision": "approved", "account": "opened", "consent": "customer_device" }
Your entire product catalogue, including liability.
Savings, current and FD originate straight through at the counter. The same agent originates a loan, sells insurance, runs AePS and enrols a scheme.
Banking
Savings, current and salary accounts, full KYC at the counter.
Liability originationLoans
Personal, business, gold and two-wheeler, decided by your rules engine.
Assisted lendingCards
Sourced, decided and issued in the sitting: instant virtual card, limit enhancement, upgrades.
Credit & debitPayments
AePS and microATM, UPI and QR, recharges and bill pay.
Last-mile railsInvestments
Mutual funds, DigiGold, RD and FD.
Wealth at the doorstepSocial security
PMJJBY, PMSBY and APY, enrolment and renewals at the doorstep.
SchemesThe lead is sourced and the loan closed in the same sitting.
The conversion loss sits in the gap between sourcing and sanction. Here the application hits the same rules engine as your branch and comes back decided while the customer is still at the counter.
- Same rules, same reason codes No last-mile policy
- Identity verified once, carried through Decision → servicing
The consent is captured on the customer’s phone. Not the agent’s.
Consent on an agent’s handset is consent you can’t later prove was informed. So the agent drives, and every consent, OTP and signature hands off to the customer’s own phone.
- Purpose-bound, language-attributed, revocable DPDP
- Every consent names the agent present Traceable by district
Account details
Confirm on your phone
Ask for the failure taxonomy.
A 98% success rate says almost nothing. What matters is whether the other 2% is diagnosed automatically, and whether the day settles without a spreadsheet.
- 98.2% succeededAePS · last 24h
- Low biometric quality→ retry with guidance0.9%
- UIDAI timeout→ auto-retry ×2, then queue0.5%
- Issuer declined→ reason shown to the agent0.4%
- Day settles→ no spreadsheetT+1
Every failure has an owner and a next step · nothing for the agent to guess
AePS transactions this hour
Success rate, and the 1.8% diagnosed
Settled today, T+1
We productised a distribution network we had already run.
Every constraint came from running one of India’s largest assisted networks. From operating experience.
Gross transaction value distributed
Retail outlets reached
First network live in about twelve weeks. Every one after that, about a week.
- Foundation · Wk 1-4Core integration
Catalogue mapped, commission grids modelled.
- Configuration · Wk 5-8Manifests & entitlements
Partner manifests, entitlement model, agent policy.
- Certification · Wk 9-12First network live
NPCI/AePS certification, UAT, pilot district.
- Scale · Wk 13+~1 week per network
Manifest → review → certify → live.
Frequently asked
A BC network sells you access to agents it owns. This is software that lets you own and manage agents, yours, your partners’, or both, operating under your institution as principal.
No. Bring the BC and DSA relationships you already have onto one interface, or plug into partner rails that are already integrated. Either way the agents work under your name.
Both. Account opening, deposits and transactions run on the same rails as loan origination. The agent already at the door is the cheapest distribution available.
Deduplication runs against your book and every in-flight application before a bureau pull is authorised, with first-touch attribution recorded.
Cards are the anchor product of the DSA module. Sourced, decided against your card policy, issued as a virtual card and transacting in the same sitting, the physical card follows.
A platform fee plus per-transaction pricing on payment rails; lending origination is priced separately. What you pay your agents is yours to set.