BMO and Mastercard have made commercial virtual cards available inside participating ERP, procurement, accounts payable and travel platforms for eligible corporate clients in Canada and the United States. A buyer can initiate and manage a BMO virtual card payment without leaving the software where the invoice or expense already lives. Mastercard calls the integration framework Commercial Express.
The more important development is that an eligible enterprise can bring a supported existing card relationship into participating operating software. It does not have to adopt a software company’s new card program. This BMO launch covers one issuer and participating platforms, not every card in every application. The broader bring-your-own-card market will be real when enterprises can use multiple existing issuer programs inside major software platforms without a new bespoke integration for each bank.
At Finexio, even the fastest third-party software integration I saw took 30 days. Three months was closer to the average before serious testing. That was only the technical connection. The bank, software company and customer’s finance team still had to agree on how a payment would be initiated, controlled, supported and reconciled.
The networks are opening another route into software
Visa describes two distinct models. In a platform-as-issuer model, a software company offers virtual cards through an issuer and may share in interchange. In a bring-your-own-card model, a larger enterprise keeps its established commercial card program while the software platform connects to Visa or the issuing bank. The platform can win retention and potentially negotiate a revenue share, but it does not automatically become the issuer or capture interchange.
Mastercard’s BMO launch is an issuer-backed instance, while Visa describes a broader model for connecting an enterprise’s existing card program. Both put credentials and payment controls inside third-party workflows. Neither announcement proves that a buyer can move any card into any platform. Broader issuer and platform coverage is the test.
Think about what changes for a corporate buyer. The team approves a supplier invoice in its procurement system, selects the card program it already uses, applies spend controls, sends payment and brings the reconciliation data back into the same workflow. Today those steps often require a banking portal, a separate card interface and someone moving information between them. Removing that swivel-chair work is the product.
BMO’s years as joint owner of merchant acquirer Moneris, which it agreed to sell in August 2026, give it experience on both the issuing and acceptance sides. That should make the work beyond the card connection familiar. Owning both the issuing and acceptance sides of one transaction can support two revenue pools on the same dollar.
An API does not build a payments journey
The networks can simplify access to credentials. They cannot decide which suppliers should receive a card, handle acceptance objections, design the exception queue or make a finance team trust the reconciliation. Visa’s own embedded-payments guidance names issuer integrations, compliance and supplier enablement as separate execution problems. Those do not disappear when a platform can call one API. In Finexio’s network, roughly a fifth of virtual card spend ran through phone and portal channels that no credential alone could reach.
Coupa illustrates the time involved. Coupa said in 2025 that it had spent seven years building Coupa Pay, which by then supported payments in almost 200 countries and more than 140 currencies. That is a substantial operating effort, not a button in an accounts-payable screen.
I spent eleven years building Finexio and its embedded B2B payment partnerships. In that work, the scarce person was the one who could sit between a bank, a network, a software product team and the customer’s finance operation, then turn a credential into a payment journey that worked. The banks I encountered moved slowly and often struggled to sell a service through a software partner. Software teams I worked with often underestimated the payments operation behind the API. Both sides need someone who has done it.
This also changes the competitive map. Some issuing processors and aggregators sell the difficulty of connecting software to card programs. If network frameworks reach enough issuers and platforms, bank-specific credential provisioning and controls exchange become less valuable as standalone services. If coverage stays narrow, those processors retain their integration advantage. Program design, onboarding, supplier acceptance and ongoing operations remain valuable either way.
For an enterprise software company, the decision is not simply whether to add cards. It is whether customers want to bring the card relationship they already have, and whether the company can deliver a better workflow around it. I help banks, software companies and investors build and evaluate those journeys. If you are working on one, contact me.
The credential is getting easier to bring in. The execution is not.