TrustField
Sandbox live on trustfield.caProgram operations and evidence for regulated programs — drift caught in CI and receipts; licensed partners remain settlement party of record.Program ops · evidence, not settlement
Start free sandboxTrustField
MSB API programs
TrustField is the program-operations API between your customer-facing MSB app and licensed fintech partners: digital asset market venues, bank-linked partner handoff, and identity providers. You keep settlement party of record; we keep workflow state, TF program IDs, and audit exports.
Settlement boundary
TrustField does not participate in settlement or custody. Your licensed MSB or institution remains settlement party of record on every commercial path.
Licensed MSB programs need an API operating layer — not six direct integrations and a spreadsheet audit trail.
Partner categories
Sandbox uses stub adapters today. Production partner handoff unlocks per partner after Integration Program SOW and partner sign-off — no production movement on TrustField.
Sandbox
Stub venue adapter · sandbox acknowledgements
Production
Licensed market venue handoff (partner MOU)
adapter · venue_a
Sandbox
Stub pay partner · no production movement
Production
EFT / account-to-account at licensed partner
adapter · pay_partner
Sandbox
Stub identity checks
Production
Licensed verification partner handoff
adapter · identity_partner
Sandbox
Full API loop on trustfield.ca
Production
Same APIs · production credentials
adapter · trustfield
Why operators deploy TrustField
Self-serve · available now
Free sandbox on trustfield.ca — full API loop without a sales call or production credentials.
Fixed Discovery SKU
CAD 4,000 RPAA Discovery and Integration Program SKUs on /pricing — scoped SOWs, not mystery quotes.
1 program ID loop
Intake, workflow state, ops alerts, and exports on one program ID — partners execute settlement.
No TrustField custody
TrustField does not hold custody or transmit money. Your licensed MSB remains settlement party of record.
API connect flow
Customer-facing intake — branded slug or embedded register
TF-###### · checklist gates · handoff record
Maps program handoff record to licensed partner rail
Venue, bank rail, or identity provider executes
Webhooks + operator console + export bundle
{ "full_name": "Sample MSB Program", "email": "ops@partner-msb.ca", "corridor": "CA", "settlement_path": "fiat", "partner_slug": "demo-msb-tor", "consent_accepted": true}→ { "program_id": "TF-000042" }
Illustrative TF-000042 — your register response will differ.
Sandbox program readiness
demo-msb-tor
Score is rule-based in sandbox — not an autonomous compliance verdict.
Try it now
Sample responses below are illustrative — register for a live TF program ID, then run the loop at /register.
POST /api/register
Program intake returns a TF program ID and opens checklist state.
{
"id": 42,
"program_id": "TF-000042",
"status": "pending",
"registration_type": "program",
"message": "Program intake received."
}One loop
Intake, workflow, partner handoff records, ops alerts, and audit exports on one TF program ID — not six disconnected tabs.
Register — Branded intake assigns TF-######
Checklist — Human gates + evidence upload
Handoff — Payload-free sandbox handoff record at /trade
Partner — Licensed partner execution (MSB-owned)
Status — API + operator console state
Export — MLRO / procurement bundles
Intake proof
Minutes
Not days in email
Manual handoffs
1 program ID
Vs spreadsheet chains
Ops visibility
Alerts
Optional Telegram ops channel
Commercial path
Published
SKUs on /pricing
For licensed MSB programs
Your program needs auditable evidence: a TF program ID, checklist gates, partner handoff, and exports counsel can review — with your MSB as settlement party of record.
Compliance & program ops
Checklist gates, document uploads, and audit bundles on the same program ID — less email-chain reconstruction every review.
See how it works →Integration & engineering
Self-serve sandbox: register → program state → status. Production partner handoff scoped on Integration SOW after the stub path proves fit.
Developer hub →MLRO & counsel review
Workflow prepares exports and gate history — filings and high-risk decisions stay with your MLRO and counsel, not autonomous bots.
Vendor brief →Six modules · one program loop
Not autonomous regulatory bots. Structured workflow modules keep program state in sync; MLRO and counsel approve anything that touches filings or settlement.
Central workflow state
Coordinates TF program ID state across intake, checklist, and handoff-record steps — keeps the program moving without manual log stitching.
Registration coach
Opens checklist on register, assigns TF-######, and surfaces next fields by program type.
Gate tracker
Scores checklist completion, highlights blocked items, and pauses workflow until operators approve evidence.
Program health score
Rule-based readiness score from checklist, corridor config, and documents — baseline in sandbox, gap map in Discovery.
Real-time ops channel
Telegram alerts on intake and key workflow events — optional Program Pulse digest for sandbox users.
Evidence bundles
Vendor brief, diligence pages, and CSV/HTML exports — counsel-ready without rebuilding reports each review cycle.
Where it runs
No copy-pasting between intake, ops console, APIs, and partner handoff — each surface gets workflow built for its role.
Branded intake
/register · partner slugs
Operator console
Checklist + workflow state
REST APIs
/developers · OpenAPI
Webhooks & alerts
Ops Telegram optional
Export bundles
MLRO · procurement
Partner handoff
MSB-owned settlement
Usage on production
Sandbox program IDs are unlimited for development. Production tiers include scoped handoff record volume — overage terms appear on Integration SOW.
| Tier | Included | Overage |
|---|---|---|
| Developer sandbox | Unlimited sandbox program IDs | No production partner handoff |
| RPAA Discovery | Assessment only | — |
| Integration program | e.g. 10k handoff records/mo | Per-1k blocks on SOW |
| Platform access | e.g. 50k+ / custom | Enterprise blocks |
Illustrative units — final volumes on scoped Integration or Platform SOW.
Partner economics
Revenue stays with the licensed MSB on every commercial path. TrustField is program workflow state and audit evidence — not a revenue share on settlement.
Customer
Uses your branded program intake
Your MSB
Settlement party of record · corridor revenue
TrustField
TF program ID · workflow · exports · APIs
Licensed partner
Executes partner handoff you approve
TrustField does not participate in settlement or custody.
90-second sandbox tour
Register
Branded intake assigns TF-######
Checklist
Human gates + evidence upload
Handoff record stub
Create payload-free handoff at /trade
Status + export
API state and audit bundle
Long-term value
Event history, export bundles, and checklist patterns build on the same TF program IDs — less rebuild every supervisory cycle. Discovery baselines readiness; Integration deploys your configured loop; Platform keeps production programs running.
Who this is for
If you need program workflow, REST APIs, and counsel-ready evidence while your MSB keeps settlement — TrustField is the layer in front of licensed partners.
TrustField records program workflow state and evidence — not custody, partner-side lifecycle decisions, or autonomous regulatory filing.
Start freeBuilt for Canada
2027 Mar 31 · Next annual supervisory reporting cycle (registered operators under RPAA) · Informational only · not legal advice
Self-serve signup and the full API loop are available at no fee. Apply for CAD 4,000 Discovery or an Integration Program when production scope is clear. Your MSB remains settlement party of record.
Questions? Contact us →GET /api/venues — integration patterns (public labels only)
{
"count": 10,
"demo_mode": true,
"venues": [
{
"public_label": "Market access A",
"tier": "P0",
"configured": false,
"sandbox_ready": false,
"live_sandbox": false,
"message": "set VENUE_A_API_KEY, VENUE_A_API_SECRET, VENUE_A_API_PASSPHRASE",
"mode": "demo"
},
{
"public_label": "Market access B",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access C",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access D",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access E",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access F",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access G",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access H",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access I",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
},
{
"public_label": "Market access J",
"tier": "P1",
"configured": false,
"sandbox_ready": true,
"live_sandbox": false,
"message": "demo mode — sandbox simulation available",
"mode": "demo"
}
]
}GET /api/integrations/health — adapter configuration (no secrets exposed)
{
"adapters": [
{
"provider": "identity_partner",
"configured": false,
"message": "set IDENTITY_PARTNER_API_KEY"
},
{
"provider": "pay_partner",
"configured": false,
"message": "set PAY_PARTNER_API_KEY and PAY_PARTNER_API_SECRET"
},
{
"provider": "venue_a",
"configured": false,
"message": "set VENUE_A_API_KEY, VENUE_A_API_SECRET, VENUE_A_API_PASSPHRASE"
},
{
"provider": "venue_b",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_c",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_d",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_e",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_f",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_g",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_h",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_i",
"configured": false,
"message": "demo mode — sandbox simulation available"
},
{
"provider": "venue_j",
"configured": false,
"message": "demo mode — sandbox simulation available"
}
]
}