Fast onboarding. Real compliance.
Your customers expect to open an account in minutes. Regulators expect you to verify their address. Trusqo lets you do both: verify proof of address documents instantly, right inside your onboarding flow.
Your customers expect to open an account in minutes. Regulators expect you to verify their address. Trusqo lets you do both: verify proof of address documents instantly, right inside your onboarding flow.
Fintechs move fast. Customers sign up on their phone, verify their identity in seconds, and expect to start using the product immediately.
But proof of address is still a bottleneck. Documents arrive in different formats, languages, and layouts. Someone has to read each one, check the details, and make a decision. That's where the onboarding flow breaks.
Customers abandon onboarding when they're told to wait for manual review
Growing your user base means growing your review team at the same rate
Documents arrive in dozens of languages and formats your team can't always read
Any company offering financial products needs to verify customer addresses. Here's how fintechs use trusqo.
Verify customer addresses during digital onboarding without branches or manual review.
EMI and PSP licence compliance requires address verification. Automate it from day one.
Confirm borrower addresses before disbursement. Reduce fraud, meet regulatory requirements.
If your platform offers financial products, you inherit KYC obligations. Add address verification via API.
Exchange and wallet providers need proof of address for licensing. Support global users in any language.
Policyholder address verification for underwriting and claims. Process documents in seconds.
Utility bill, bank statement, government letter, or insurance document. Send it via API or the dashboard alongside the expected name and address.
curl -X POST https://app.trusqo.com/api/verify \ -H "X-API-Key: $TRUSQO_KEY" \ -F "name=James L. Whitford" \ -F "address=15 Rue de la Paix, Paris" \ -F "[email protected]"
Trusqo reads the document in any language, extracts name, address, date, and document type. Non-Latin scripts are transliterated automatically.
James L. Whitford
15 Rue de la Paix, Paris
bank-statement
A clear pass or fail verdict with per-field match scores and a downloadable PDF report. Everything a regulator needs during an audit.
{
"status": "approved",
"nameMatchScore": 0.92,
"addressMatchScore": 0.96,
"extractedDocType": "bank-statement"
}
Automated checks in under 3 seconds. Your team reviews edge cases, not every document.
Every verification logged with extracted data, match scores, and decision reasoning. PDF reports for your compliance files.
Documents in any script processed natively. Automatic transliteration keeps your records in one alphabet regardless of the original language.
Match thresholds, document age limits, and accepted types per your risk appetite. Adjust per request as regulations change.
POST /api/verify
Content-Type: multipart
→ 202 Accepted
→ { "requestId": "a1b2…" }
A single REST endpoint. Send the document, get a structured result with evidence.
All data processed and stored in the EU. Documents deleted automatically after retention.
Research shows 40–70% of prospects drop off during KYC onboarding. Document upload and waiting for manual review are the two biggest friction points.
Trusqo doesn't just read the text. Every document is analysed for signs of tampering, checked against its metadata, and classified by type before a verdict is returned.
Utility bills, bank statements, government letters, insurance documents, medical bills, pharmacy bills, post office letters, and life insurance documents. You control which types are accepted per request, and trusqo auto-detects and rejects anything that doesn't match.
Most documents are verified in under 10 seconds. The API accepts the request asynchronously: you can poll for the result or receive it via webhook.
Yes. Trusqo processes documents in 50+ languages and scripts including Arabic, Cyrillic, Chinese, Japanese, Korean, Thai, and Hebrew. Non-Latin text is automatically transliterated to Latin characters for matching.
A single REST endpoint. Send a multipart POST with the document file and the expected name and address. Get back a request ID, then poll or use webhooks for the result. Full API docs are at docs.trusqo.com.
Yes. Your operations team can submit, review, and manage verifications from a clean web interface without writing any code. The dashboard includes document preview, match details, and PDF report downloads.
In most jurisdictions, yes. ID verification confirms who someone is, but proof of address confirms where they live, a separate regulatory requirement under KYC and AML frameworks. EMI, PSP, and banking licences typically require both.
You get a structured response with the reason: mismatched name, expired document, unsupported document type, or low match scores. Your onboarding flow can prompt the customer to upload a different document automatically, no manual review needed for clear-cut failures.
Yes. Use the same API endpoint for ongoing monitoring. Many regulators expect periodic re-verification every 1–3 years, and some risk-based frameworks require it on trigger events like address changes.
No contracts, no minimums, cancel any time. Every plan includes the full API, dashboard, and webhooks.
curl -X POST https://app.trusqo.com/api/verify \
-H "X-API-Key: poa_live_..." \
-F "[email protected]" \
-F "name=John Doe" \
-F "address=123 Main St"