MSB & Exchange Operations Automation

The operating layer between your MSB app and regulated partner APIs

TrustField builds and operates workflows between customer intake, compliance approvals, exchange and payment partners, reconciliation, and audit trails. Registered MSBs, PSPs, banks, and exchanges execute regulated transactions; TrustField runs the workflows, controls, integrations, and operational records. The customer remains the Reporting Entity.

See Workflow Samples Discuss an integration

Settlement boundary

TrustField does not itself provide custody or settlement services. Applicable custody and settlement activities remain with the customer’s designated providers.

MSBs and exchange operators need one operating layer — not six direct integrations and a spreadsheet audit trail.

Partner categories

One program workflow API · multiple regulated partner types

Sandbox uses stub adapters today. Production partner handoff unlocks per partner after Integration Program SOW and partner sign-off — no production movement on TrustField.

Digital asset market APIs

Venue class

Sandbox

Stub venue adapter · sandbox acknowledgements

Production

Licensed market venue handoff (partner MOU)

Order handoff record
Status callbacks
Corridor-scoped handoff

adapter · venue_a

Bank-linked partner handoff

Payment partner

Sandbox

Stub pay partner · no production movement

Production

EFT / account-to-account at licensed partner

Partner handoff records
Partner settlement handoff
No TrustField custody

adapter · pay_partner

Identity & verification APIs

KYC partner

Sandbox

Stub identity checks

Production

Licensed verification partner handoff

Checklist evidence hooks
Verification status events
MLRO export fields

adapter · identity_partner

TrustField program API

Core

Sandbox

Full API loop on trustfield.ca

Production

Same APIs · production credentials

Register · checklist · trade
Webhooks · ops alerts
Export bundles

adapter · trustfield

Why operators deploy TrustField

Software you can try, price you can publish, boundary you can defend

Self-serve · available now

Try before you scope

Free sandbox on trustfield.ca — full API loop without a sales call or production credentials.

workflow deployment

Published program packages

Controlled Production Launch and Managed Operations packages on /pricing — scoped SOWs, not mystery quotes.

1 program ID loop

Operating layer, not a tab

Intake, workflow state, ops alerts, and exports on one program ID — partners execute settlement.

No TrustField custody

Settlement stays with you

TrustField does not hold custody or transmit money. Designated providers remain settlement party of record.

Live operations workflow

From intake to audit export

01
Intake
Customer or transaction intake into a structured program record
02
Compliance checks
Identity and compliance gates before handoff
03
Maker-checker
Operator approval with immutable event history
04
Partner routing
Exchange or payment-partner selection and API handoff
05
Callbacks & recon
Status callbacks, reconciliation, exceptions, audit export

{  "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.

Integration health

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"
    }
  ]
}

Market access catalog

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"
    }
  ]
}

Try it now

Preview the sandbox API loop

Sample responses below are illustrative — register for a live TF program ID, then run the loop at /register.

Sample response · not live dataIllustrative TF-000042 — your register response will differ.

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."
}

Technical sandbox OpenAPI docs →

One loop

Register → handoff → status → export — connected in one system

Intake, workflow, partner handoff records, ops alerts, and audit exports on one TF program ID — not six disconnected tabs.

Register
Checklist
Handoff
Partner
Status
Export

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 Canadian payment-program operations

Prove the program loop in sandbox before you scope production

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

One TF program ID from intake to export

Checklist gates, document uploads, and audit bundles on the same program ID — less email-chain reconstruction every review.

See how it works →

Integration & engineering

OpenAPI loop in minutes, not a quarter

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

Evidence packs for human sign-off

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

Program workflow modules — your team signs off on compliance

Not autonomous regulatory bots. Structured workflow modules keep program state in sync; MLRO and counsel approve anything that touches filings or settlement.

Program orchestrator

Automated state

Central workflow state

Coordinates TF program ID state across intake, checklist, and handoff-record steps — keeps the program moving without manual log stitching.

Intake workflow

Automated intake

Registration coach

Opens checklist on register, assigns TF-######, and surfaces next fields by program type.

Checklist coach

Human sign-off

Gate tracker

Scores checklist completion, highlights blocked items, and pauses workflow until operators approve evidence.

Readiness scanner

Rules + review

Program health score

Rule-based readiness score from checklist, corridor config, and documents — baseline in sandbox, controls in the operating platform.

Ops alerts

Configurable alerts

Real-time ops channel

Telegram alerts on intake and key workflow events — optional Program Pulse digest for sandbox users.

Export packager

Human release

Evidence bundles

Vendor brief, diligence pages, and CSV/HTML exports — counsel-ready without rebuilding reports each review cycle.

Where it runs

One platform across every program surface

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

Included API handoff records per tier

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
Controlled Production Launch	Live operating workflow	—
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

Your MSB monetizes the corridor. TrustField runs program ops.

Revenue stays with designated settlement providers on every commercial path. TrustField is program workflow state and audit evidence — not a revenue share on settlement.

1
Customer
Uses your branded program intake
2
Your MSB
Settlement party of record · corridor revenue
3
TrustField
TF program ID · workflow · exports · APIs
4
Licensed partner
Executes partner handoff you approve

TrustField does not participate in settlement or custody.

90-second sandbox tour

See the loop before commercial scope

0:00
Register
Branded intake assigns TF-######
0:20
Checklist
Human gates + evidence upload
0:45
Handoff record stub
Create payload-free handoff at /trade
1:00
Status + export
API state and audit bundle

Assessment Full showcase walkthrough

Long-term value

Your program history compounds on one workflow layer

Event history, export bundles, and checklist patterns build on the same TF program IDs — less rebuild every supervisory cycle. Controlled Production Launch puts the loop live; partner integrations connect rails; Managed Operations keeps production running.

Who this is for

Built for Canadian payment operations and compliance teams

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.

Canadian payment operations and compliance teams running supervised payment programs
Branded intake and TF program IDs for every application
Sandbox proof before Integration or production partner handoff conversations
REST APIs and exports for ops, engineering, and MLRO review
Partner handoff without TrustField holding custody

TrustField records program workflow state and evidence — not custody, partner-side lifecycle decisions, or autonomous regulatory filing.

Assessment

MSB API FAQs

Does TrustField connect directly to crypto exchanges?: TrustField orchestrates program handoff records for licensed digital asset market venue APIs configured for your program. Venues remain execution parties — TrustField does not hold assets or settle trades.
Can I try rail connections without production credentials?: Yes. Sandbox mode uses stub adapters — full register → program state → status loop with sandbox acknowledgements. Production credentials require Integration Program SOW and partner approval.
Who holds custody and settlement risk?: Designated providers remain settlement party of record. TrustField records workflow state and prepares payload-free handoff records — partners execute movement.

Assessment Partner handoff overview Integration program

Built for Canada

RPAA-era program infrastructure for supervised operators

BoC RPAA supervision RPAA legislation PSP registry FINTRAC MSB Compliance hub →

2027 Mar 31 · Next annual supervisory reporting cycle (registered operators under RPAA) · Informational only · not legal advice

Launch one real workflow with Launch Care included

See a public sample, confirm scope if you want, then start Controlled Launch for CAD 4,900. Expand later to Connected Production or Managed Care. Your organization remains the Reporting Entity.

Start Controlled Launch View packages

Questions? Request a Workflow Proof →

The operating layer between your MSB app and regulated partner APIs

One program workflow API · multiple regulated partner types

Digital asset market APIs

Bank-linked partner handoff

Identity & verification APIs

TrustField program API

Software you can try, price you can publish, boundary you can defend

Try before you scope

Published program packages

Operating layer, not a tab

Settlement stays with you

From intake to audit export

Intake

Compliance checks

Maker-checker

Partner routing

Callbacks & recon

Integration health

Market access catalog

Preview the sandbox API loop

Register → handoff → status → export — connected in one system

Prove the program loop in sandbox before you scope production

One TF program ID from intake to export

OpenAPI loop in minutes, not a quarter

Evidence packs for human sign-off

Program workflow modules — your team signs off on compliance

Program orchestrator

Intake workflow

Checklist coach

Readiness scanner

Ops alerts

Export packager

One platform across every program surface

Included API handoff records per tier

Your MSB monetizes the corridor. TrustField runs program ops.

See the loop before commercial scope

Your program history compounds on one workflow layer

Built for Canadian payment operations and compliance teams

MSB API FAQs

RPAA-era program infrastructure for supervised operators

Launch one real workflow with Launch Care included