White-label and platform
Your client never has to know our name.
Trust Ledger runs under your brand: your logo, your colours, your domain. Send clients to a branded page, or embed the whole thing inside the product you already sell, so it reads as yours because it is yours.
- Full white-label, including the signing and collection experience
- An API, keys you control, and webhooks into your own systems
- A sandbox that cannot touch live client data
Two ways to run it
Build on it, or simply use it.
The same platform underneath, whichever way you take it.
The API
One request, every party, in one call.
Create the request, add the parties and their checklists, attach the document and its zones, and send. The same object the interface builds.
POST /v1/requests
curl -X POST https://api.trustledger.net/v1/requests \
-H "Authorization: Bearer $TRUST_LEDGER_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "1420 Simcoe St, lease and guarantee",
"parties": [
{ "role": "applicant", "email": "[email protected]", "verify": "biometric" },
{ "role": "co_applicant", "email": "[email protected]", "verify": "biometric" },
{ "role": "guarantor", "email": "[email protected]", "verify": "2fa" }
],
"sequence": "strict",
"document": { "file_id": "doc_9f2c", "zones": "template_lease_v4" },
"checklists": { "applicant": ["photo_id", "pay_stub", "reference"] },
"webhook": "https://your-app.example.com/hooks/trust-ledger"
}'Webhooks
Your systems find out at the same moment we do.
Every state change on a file is an event you can subscribe to, signed so you can verify it came from us.
- request.sent, party.opened, identity.verified, item.submitted, item.returned
- document.signed, round.superseded, request.closed, profile.updated
- Signed payloads, retries with backoff, and a replay endpoint for anything you missed
Talk to us about licensing.
White-label licensing, embedded deployments and volume pricing are handled directly. Book twenty minutes and bring your architecture.