A new revenue line
Earn a partner share on authentication your clients run through your platform, on terms agreed with you.
Partners · Loan management systems
Put bank-statement authentication inside your lending platform.
Integrate OptiTrust once and offer document authentication to every credit provider on your platform. Your clients see authenticity verdicts in the loan file they already work from.
What it gives your platform.
Statement fraud checks are something your credit-provider clients need. You can offer them without building or maintaining a detection engine yourself.
A stronger product
Offer document authentication as a built-in feature of your lending workflow, not an add-on your clients have to find elsewhere.
No engine to build
OptiTrust runs the statement checks and maintains them. You integrate one REST API and one webhook contract.
Your clients keep their workflow
Credit teams stay in your system. The verdict, risk band, and the issues behind it arrive with the application.
Why credit providers need it
Affordability decisions rest on bank statements.
National Credit Act affordability assessments depend on income and expense evidence, and bank statements are usually central to it. An edited or fabricated statement undermines the whole assessment.
- Detects tampered, manipulated, or fabricated PDF statements before a credit decision.
- Shows the issues behind each verdict, so a reviewer can defend the decision.
- Reports statements it could not assess, such as unsupported or password-protected files, separately from fraud.
How the integration works
Your platform calls the OptiTrust API with the API key of the credit provider it is acting for. Each request is scoped to that client's account.
-
01
Create a bundle
When an application needs statements, create a bundle through the API with the required period and your webhook URL.
-
02
Upload statements
Request a server-issued upload target for each PDF, upload it, and complete the attachment. No shared storage access is needed.
-
03
Receive signed webhooks
OptiTrust sends HMAC-signed events as files are added and the bundle status changes.
-
04
Attach the result
Fetch the bundle for each file's verdict, risk band, and issues, and store it on the loan file.
Everything your developers need.
The API reference, upload flow, and webhook contract are public. Review them before the first call.
Swagger API reference
Endpoints, request bodies, response models, and status codes for statement bundles.
Open Swagger (opens in a new tab)Bundle and webhook guide
The upload sequence, event types, signature verification, and delivery behaviour.
Read the bundle guideDeveloper hub
API keys, integration endpoints, current traffic limits, and an integration skill file for AI coding assistants.
Visit the developer hubPartner model
You integrate once. Each client keeps its own account.
- Each credit provider opens its own OptiTrust account and issues an API key for your platform to use.
- OptiTrust bills each credit provider directly, so you carry no credit or collection risk.
- Every client's documents and results stay separate, scoped to its own account.
- You earn a partner share on authentication run through your platform, on terms we agree with you.
- Test access before go-live is arranged with our team.
Data protection
Built for POPIA from the start.
- The credit provider stays the responsible party for its applicants' data. OptiTrust processes it as an operator.
- Data is used only to deliver the checks the client requested.
- Each client account controls its own data-retention window.