For regulated programs
Compliance and regulation
Background for teams running regulated programs on TrustField. Your counsel owns filings and licensing decisions.
Built for Canada
RPAA-era program infrastructure for supervised operators
2027 Mar 31 · Next annual supervisory reporting cycle (registered operators under RPAA) · Informational only · not legal advice
What TrustField provides
TrustField is workflow software for regulated market programs: intake, operator tools, an audit trail, and connections to licensed partners. Your counsel still owns filings and licensing strategy.
RPAA timeline
Payment service providers could begin registering with the Bank of Canada under the RPAA.
Operational risk and safeguarding rules took effect for registered operators.
First annual supervisory reporting cycle for registered operators (completed).
Next annual supervisory reporting cycle for registered operators.
TrustField continues shipping API programs and partner integrations for Canadian operators.
Supervisory context · Canada
Software aligned to the RPAA supervisory cycle
Registered payment service providers face heightened evidence and reporting expectations under Bank of Canada supervision. TrustField helps supervised programs run documented intake, workflow state, and exportable audit trails — your counsel and MLRO still own filings and regulatory strategy.
Mar 31
2027 Mar 31
Next annual supervisory reporting cycle (registered operators under RPAA)
Documented program flows
Structured intake, checklist, and status — evidence your supervisors and MLRO can review without ad-hoc spreadsheets.
Operational risk readiness
Sandbox and production paths designed for supervised programs — safeguarding and execution remain with licensed partners.
Exportable evidence
TF program IDs, event history, and diligence exports packaged for vendor review and annual reporting prep.
TrustField is not the Bank of Canada, not a registered operator today, and does not submit supervisory reports or filings on your behalf. Full compliance context →
Five payment functions — where TrustField sits
Canada’s retail payments framework describes authorization, clearing, settlement, and related functions. TrustField orchestrates program workflow and evidence — licensed partners perform movement and settlement.
Authorization & initiation
Customer and operator actions that start a program handoff record — intake, verification, and API submission.
TrustField: workflow state + TF program ID
Clearing partner handoff
Mapping program handoff records to the correct licensed partner rail or market venue path.
TrustField: program workflow handoff — partner executes
Settlement
Movement and final settlement party of record obligations.
Designated institution / settlement partner — not TrustField
Safeguarding & records
Evidence, audit trail, exports, and checklist documentation for supervisory review.
TrustField: export bundles + diligence pages
Supervision readiness
Structured flows aligned to RPAA-era program expectations — counsel owns filings.
TrustField: discovery + integration programs
Educational context for MLRO review. TrustField does not claim to perform all payment functions today.
Partner handoff →Retail payments in Canada
If your program falls under Canada's retail payments framework, you may need registration and safeguarding standards with the Bank of Canada. RPAA workflows apply only where you perform in-scope retail payment activities — crypto-only exchange activity is not automatically in scope; applicability depends on the payment functions actually performed. TrustField helps you run structured flows and keep evidence — it does not replace your lawyer or your filings.
Bank of Canada — retail payments supervision →AML and KYC
Your program may have its own AML and KYC obligations. TrustField's checklist and document tools help your team stay organized. We do not file on your behalf.
Where TrustField sits
Your customers interact with your program through TrustField. When execution is required, handoff records prepare for licensed market and program operations infrastructure downstream.
Audit-grade TF IDs and exports
Every program receives a unique TF program ID. Operator actions flow through checklist, status, and event history your MLRO can export — HTML and CSV bundles for vendor review, plus print-ready diligence briefs per program.
- ✓TF-###### program ID on intake — visible on status, checklist, and diligence pages
- ✓Structured checklist and document evidence — not a substitute for your filings
- ✓Compliance export and diligence brief — for counsel and MLRO review folders
- ✓Positioning CI on ship — public copy cannot drift into PSP or custody claims
What you can hand to procurement
Vendor brief (print PDF), per-program diligence page, and scoped admin export on sandbox programs — packaged for MSB vendor review without claiming TrustField files with regulators on your behalf.
Licensed partners remain responsible for their own registrations and movement flows. This page is 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 regulated entity.
Questions? Request a Workflow Proof →