MSP channel
Licensed partner complement
Execution partner vs TrustField orchestration and evidence
Ref: TF-MSP-PACK-v1 · Version: 2026-06-03 · hello@trustfield.ca
Licensed payment and market-access partners execute movement and settlement. TrustField sits in front: program intake, workflow state, and audit-grade program IDs — complement, not replace.
| Dimension | Licensed execution partner | TrustField |
|---|---|---|
| Primary role | Payment accounts, rails, and execution APIs | Program workflow software and REST APIs |
| Who moves money | Licensed institution or CaaS partner | Does not — designated MSB or partner remains settlement party |
| Customer intake | Partner-dependent configuration | Branded /register, TF program ID, checklist |
| Audit evidence | Partner statements and API logs | TF program ID lifecycle, events, export bundles |
| Typical buyer | Treasury / payments engineering | Program ops, MLRO, integration lead |
| Phase fit | When execution path is chosen | Readiness advisory through program software deployment |
| Partner motion | Rail and account setup | Channel MSP sells advisory + deploys TF software |
Talk track
- We complement licensed execution partners — MSBs get ready and run the program layer before and alongside production rails.
- Your MSB client keeps settlement party of record; TrustField never holds funds.
- Discovery proves the gap map; integration program wires TF program ID + exports to the partner stack.
TrustField does not participate in settlement or custody.