FIS has launched a platform that puts bank accounts, cards and payment tools inside business software. Here is what UAE ERP, accounting and marketplace providers should take from it.
FIS has launched an embedded banking platform for banks and software providers. It lets a bank place accounts, card issuing, receivables, payables and expense management inside the business software its customers already use. For a UAE software company, the practical lesson is not to copy the announcement blindly. It is to decide which financial task should happen inside its own workflow, then check whether a bank or licensed payments partner can support it.
The announcement was made on 3 September 2026. FIS says the platform is designed for banks to work with vertical software providers and fintechs. Pilot banks include Cogent Bank, Commercial Bank of California and M&T Bank, with accounts and payments planned for the fourth quarter of 2026. The launch is aimed at US banks, so this is not evidence that the product is already available for UAE deployment. (fisglobal.com)
The important shift is from “open the bank portal” to “complete the money task inside the software”.
The bank supplies the accounts and payment capabilities. The software provider supplies the customer-facing experience. FIS supplies the infrastructure between them. A business user can then open an account or move money without leaving the accounting, planning or operating system used each day. (fisglobal.com)
FIS says providers can connect through APIs, software development kits, embeddable widgets or white-labelled applications. That gives a platform owner several implementation routes. An API may suit a product team that wants control over the interface. A widget may be more suitable when the business wants a narrower integration with less front-end work. A white-labelled application sits further towards a ready-made banking experience.
The other important design choice is where the account sits. FIS says accounts remain on the bank’s own balance sheet rather than on a third-party virtual ledger. The bank keeps the customer relationship and regulatory control, while the software partner owns the user experience. (fisglobal.com)
For a UAE ERP, accounting, payroll, procurement or marketplace platform, embedded banking makes payments part of the product rather than a separate destination. A marketplace could show a receivable and start the collection workflow in the same place. An ERP could connect an approved payable to a payment instruction. An accounting product could present account information beside the records that explain it.
That does not mean every UAE software provider should become a bank or build a payment rail. It means the product roadmap can be tested against a simple question: where does the customer leave the system because money is involved?
A UAE platform should also separate the user experience from the regulated financial service. The FIS model keeps the bank responsible for the account while the software provider manages the interface. That distinction is likely to matter when a local provider assesses partners, data responsibilities, onboarding, transaction controls and customer support. Those are planning considerations, not proof that a particular UAE structure is approved.
For a small business using software rather than selling it, the impact is more modest. You may eventually see banking, collections or expenses appear inside an ERP or marketplace. But the sensible response today is not to replace a working system because a US technology company has announced a platform.
Start with one workflow and one customer group. Do not begin with a promise to provide “all-in-one finance”.
A worked example would be a UAE wholesale platform where a buyer approves an invoice, the seller sees the receivable, and the operator wants the payment status returned to the same screen. The first product question is not whether to issue cards. It is whether the payment status can be trusted, matched to the right invoice and explained when it fails.
This is where an existing ERP and automation setup can help a business map its current hand-offs before it considers a deeper financial integration. A smaller retailer may first need a reliable flow between sales, stock, invoices and accounts. The question of what a small UAE retail business should look for in an ERP comes before adding banking features.
Paknology has a commercial interest where the next step is ERP and automation, a website or a mobile app. Its ERP and automation service can be relevant when a UAE business needs to organise workflows before asking a provider about embedded payments.
That is not the same as supplying bank accounts, issuing cards or acting as the regulated financial institution in the FIS model. If the business only needs basic invoicing, reconciliation or a bank portal, a cheaper or simpler existing setup may serve it better than a custom integration.
The next step is to write down one money workflow, its current hand-offs and the failure points. If the gap is mainly operational software, review the ERP route; if the gap is a regulated banking product, speak to the relevant bank or financial technology partner before commissioning development.
Book a free consultation and get a clear roadmap — from company formation to a fully automated digital operation.