Flywire adds open banking payments in the US and Canada: what operators should watch

Flywire said on August 12, 2026 that it expanded its Trustly partnership to support open banking payments in the US and Canada. The company said the flow lets payers authorize secure, large domestic and cross-border payments directly from their bank accounts and in local currency. That matters because bank-led payments are increasingly being used for higher-value transactions where card limits, manual bank transfers, and reconciliation friction can slow down collections.

The news is less about consumer checkout than about payment routing for larger business flows. Open banking payments can reduce the number of steps between authorization and bank-funded payment, but they still require careful handling around confirmation, settlement timing, and exception management. Flywire’s announcement fits a broader trend in which payment providers extend bank-based rails to serve education, travel, healthcare, and other sectors that need reliable funding from bank accounts rather than card networks.

What changed and why it matters

Flywire is broadening an existing Trustly relationship into the US and Canada, which suggests a push to make bank-authorized payments more usable across North American corridors. For operators, the practical value of open banking is not just payment initiation. It is also the ability to support local currency funding, lower operational friction on larger payments, and create a cleaner path from authorization to reconciliation.

That is why this category keeps drawing attention from finance teams and payment product owners. A bank redirect or authorization is only one step in the process. The merchant still needs final payment state, ledgering, and a reliable exception path before fulfillment or release of goods and services.

Operational limits and failure modes

One clear limitation is that open banking coverage is not universal. Availability, rails, currencies, and settlement assets depend on market coverage and the capabilities enabled for the organization. That means operators should not assume a single bank-payment flow will work the same way across the US, Canada, and other regions. The practical response is to map payment methods by corridor, define what counts as a final successful state, and assign ownership for failed authorizations, reversals, and delayed settlement.

Another issue is that high-value payments tend to amplify edge cases. If a payer abandons authorization, if bank connectivity is interrupted, or if the payment lands in an unexpected state, the finance team needs a documented reconciliation process. In practice, that means treating open banking as part of a wider payment operations stack rather than as a standalone checkout button.

What to watch next

The next question is whether more payment providers use open banking to handle larger domestic and cross-border flows where bank-funded payment is a better fit than cards. If that happens, the operational conversation will shift from “can we accept bank payments?” to “how do we reconcile them, settle them, and move value onward efficiently?”

For businesses building around bank-led collection, settlement, and treasury workflows, the underlying challenge is the same. Payment initiation is only useful if the back office can follow it through to settlement and reporting. Radom’s open banking payments page is relevant here for teams evaluating bank-led collection with settlement and reconciliation in mind, especially where crypto or stablecoin workflows sit on the other side of the ledger.