
The Payments Pulse: The Controls Now Ship With the Rail
Author
November 16, 2026
Canada switched on its Real-Time Rail on November 9, and you can’t send a payment on it without passing a fraud check. Confirmation of Payee, a transaction safety score and a shared risk list are compulsory for every participant from day one. Payments Canada says no other G7 country has launched a real-time system that way.
That’s the shift we want to talk about this week: the controls now ship with the rail. For years, merchants and PSPs added fraud checks, consent capture and limits on top of whatever rail they used. This week the rail operators, card networks and regulators built them in, and a competition authority went after a rule one wallet had written into its own terms. Five stories from the past seven days.
For a high-risk merchant, this changes the question. You used to ask what your provider allowed. Now you need to know what the rail itself will refuse.

1. Canada builds the fraud check into the rail
The Real-Time Rail clears and settles around the clock, every day of the year, on ISO 20022. Eight participants went live at launch, among them Wealthsimple, KOHO, Paramount Commerce, Peoples Trust and Bank of America, with the big banks joining on a rolling basis. Interac runs the technical operation and is the first fraud services provider. American Banker notes the launch comes more than ten years after the project was announced.
The order matters more than the delay. The UK launched instant payments first and spent the next decade retrofitting APP fraud controls. Canada started with them. In the UK, a Payments Association poll published this week found 63% of respondents think real-time data sharing between firms will decide whether the national fraud strategy works. Canada has made that sharing part of the scheme.
Picture a PSP paying out refunds to Canadian customers. A payee-name mismatch now stops the payment before it leaves, which is good for fraud losses and awkward if your customer records are messy.
Related: The Payments Pulse: Trust Is Becoming the Rail
What operators should do: clean the payee names in your Canadian payout file before you route anything over the new rail.
2. Agent checkout gets a token, and a bank shuts the side door
OpenAI launched ChatGPT Wallet on November 13 with American Express, Mastercard and Visa. It’s limited for now to US Pro subscribers aged 18 or over, inside OpenAI’s “dots” agents. According to OpenAI’s announcement and 9to5Mac’s write-up, the user reviews the items, total and card, then approves with a security check such as Face ID. The network issues a token with its own card number, code and expiry. The agent never sees the real card.
The same day, PYMNTS, citing the Wall Street Journal, reported JPMorgan is blocking agents that shop with a Chase card number the customer has handed over. Bank of America, Capital One and Citigroup cards already work that way. Merchants told the WSJ the workaround, one-time virtual cards, costs more to accept and makes returns harder.
Read together, the message is clear. Agent spending is being pushed onto network tokens with consent captured at the moment of purchase, and the largest US issuer is closing the other route. Decrypt reports OpenAI plans to add delegated purchases within spending limits later, with no date yet.
Related: The Payments Pulse: The Checkpoint Moves Inside the Payment
What operators should do: check that your fraud rules don’t score a tokenised, biometrically approved agent order as bot traffic.

3. Thailand puts a number on stablecoin transfers
Thailand’s Securities and Exchange Commission has proposed a daily cap of 5 million baht, about $147,750, on individual customers’ stablecoin deposits and withdrawals at each licensed platform, The Block reported on November 13. Transfers would be allowed only between wallets belonging to the same person. The regulator also wants transfer values to match the customer’s income and financial position. Comments close November 26.
The regulator isn’t trying to police the chain. It’s turning the licensed on-ramp into the checkpoint, with a hard limit and a wallet-ownership rule. Peer-to-peer transfers outside registered platforms aren’t covered, which tells you exactly where the control is meant to sit.
Imagine a merchant settling with Thai partners through a local exchange. A large single-day payout to a partner’s wallet would breach both the cap and the same-owner rule under this draft.
Related: The Payments Pulse: Regulation Is Moving From the Merchant to the Rail
What operators should do: ask your Thai exchange partners how they’ll prove wallet ownership if the draft holds.
This isn’t legal advice.
4. Part of the US hemp ban is already live
The new federal hemp definition, signed on November 12, 2025, kicked in a year later in two stages. Since November 12, 2026, products containing cannabinoids the plant can’t produce naturally fall outside federal hemp, CannaWize and Church Law Group report. THC-O is the clearest example. Delta-8 is disputed, because no federal list has been published. On December 11 the rest follows, including a cap of 0.4 mg total THC per container.
For acquirers this is about as clean as a risk change gets. A product that was arguably fine on November 11 lost its safe harbour the next morning, and most full-spectrum edibles and drinks follow in under four weeks. A merchant’s own category label won’t carry the underwriting any more. Product-level data will.
Related: The Payments Pulse: The Perimeter Is Tightening on Every Rail at Once
What operators should do: audit every SKU against both dates, and have lab certificates ready before December 11.
This isn’t legal advice.
5. Germany challenges a rule PayPal wrote for itself
On November 11 Germany’s competition authority said in a preliminary assessment that PayPal’s ban on merchant surcharges, in place since 2018, may breach German and EU competition law. It’s also weighing whether PayPal should give up the benefit it gained. The authority notes surcharges for PayPal would be allowed in principle if they don’t exceed actual costs. This isn’t a final decision, and PayPal can respond.
Rails carry commercial rules as well as safety ones. A no-surcharge clause protects a wallet’s share by stopping merchants pricing it by cost. If the finding holds, a German merchant could charge more for the expensive method or discount the cheap one.
What operators should do: work out your true per-method cost in Germany now, so you’re ready to price on it.
This isn’t legal advice.

What this means for operators
When controls live inside the rail, your data has to fit the rail’s checks before the payment starts. Three things decide whether you pass. Clean payee records for real-time payouts. Token support and consent evidence for agent orders. Product-level detail for anything an underwriter might reclassify.
Here’s how that plays out in an ordinary week. A Canadian payout fails a name check on Monday. An agent order on Tuesday arrives with a network token your fraud engine has never seen. On Wednesday your acquirer asks which of your SKUs contain converted cannabinoids. Each of those used to be a conversation with a provider. Now the rail answers first.
The PayPal case is the other side of the same coin. Rules written into a rail can be challenged, and when they fall, merchants get pricing room they didn’t have.
The bottom line
The checks used to sit with the merchant. This week they shipped with the rail: payee checks in Canada, tokens and biometrics in agent checkout, caps in Thailand. Operators whose data already fits those checks will move money while everyone else is still fixing records.
.png&w=640&q=75)