Merchant of Record vs PSP: Why the Contractual Role Matters

A payment service provider stands in the middle of someone else's sale: it accepts funds a payer owes to a payee and moves them along. A merchant of record is structurally different — it is the legal seller. It contracts with the buyer as principal, owns the tax, refund and chargeback liability for that sale, and then, in a separate step, remits proceeds to the underlying supplier. One customer payment, two legs: a purchase (buyer to merchant of record) and a settlement (merchant of record to supplier).

The distinction matters because Canada's money services business definition turns on activities, not business models. PCMLTFA s. 5(h)(ii) captures businesses that transfer funds, and s. 5(h.1)(ii) captures foreign businesses directing that service at people in Canada, with registration required under PCMLTFA s. 11.1. A business that genuinely buys and sells in its own name is paying its own commercial debts when it pays suppliers; a business that moves money belonging to others is doing something the Act may treat as an MSB.

The scope analysis does not end because a contract says "merchant of record." The pressure point is the remit-onward leg. If the reseller role is thin — the platform never sets prices, carries no real commercial risk, and simply forwards each incoming payment to the supplier minus a fee — the arrangement starts to look like transferring other people's funds with extra paperwork around it.

Settlement control remains a key fact under any label: whose name is on the account holding the funds, who decides when and where proceeds move, and whether the business can hold back, net or redirect amounts. The definitions in PCMLTFR s. 1(2) are read against what actually happens to the money, so businesses typically map the funds flow account by account before they argue about labels.

FINTRAC withdrew its earlier policy interpretations on merchant servicing and payment processing — the PI-7670 positions — effective April 27, 2022, and reiterated the withdrawal in a further notice on July 21, 2022. Any structure assessed on the strength of those older interpretations needs re-assessment against the Act, the Regulations and FINTRAC's current MSB guidance. Where a model sits close to the line, the usual practice is to write down the contractual analysis and the funds flow, reach a reasoned conclusion, and — if genuine doubt remains — put the fact pattern to FINTRAC rather than rest on the label.

For a payments business that is within scope — or that runs AML controls because banking partners expect them — refunds and chargebacks are not just customer-service events. Patterns in them can surface fraud, merchant abuse, mule activity, sanctions exposure and transaction laundering, where a merchant account quietly processes sales for an undisclosed business.

Concrete signals worth designing for: a merchant whose refund ratio sits far outside its sector's norm; refunds directed to cards or accounts other than the one that paid; chargeback loops recurring across seemingly unrelated merchants; refunds used to move value out shortly after it arrives. Businesses typically set review thresholds for these patterns and record what was reviewed and what was decided.

Recurring subscription payments look routine, and that is exactly why they need deliberate monitoring rules. Repetition makes anomalies visible if anyone is looking: sudden changes in charge amounts, card-testing bursts against a subscription product, a spike in sign-ups from a single region, or a "subscription" merchant whose refund and churn behaviour does not resemble a subscription business. Merchant risk categories shape the profile — a newsletter platform and a high-risk digital-goods seller do not warrant the same scrutiny. The scope question, meanwhile, is unchanged by the billing pattern: it turns on how the funds are handled, not on whether charges are one-off or recurring.

Whatever the conclusion, the record matters more than the label. A defensible file typically holds the contractual analysis (who sells to the buyer, who bears refund and chargeback liability), a funds-flow map naming each account and who controls it, the scope conclusion with its reasoning and date, and evidence of re-assessment whenever the model changes. If the business is within scope, PCMLTFA s. 9.6 and PCMLTFR ss. 156–157 require a compliance program — a compliance officer, policies and procedures, a risk assessment, training and a two-year effectiveness review — and the refund, chargeback and recurring-billing indicators above belong in its written procedures rather than in one analyst's head.