Embat's J.P. Morgan link swaps certificates
Embat says J.P. Morgan's new BAS API cuts bank onboarding from months to days. The open question is what it does to bank-switching costs.
Embat's integration of J.P. Morgan Payments' banking authorization service API shifts treasury connectivity from certificate paperwork to a signed authorization. Embat says setup falls from months to days. The change is operational rather than economic: it removes onboarding friction but, on the evidence so far, adds no disclosed pricing or volume.
The Ledger Desk · 3 min read- Embat announced on Nov. 4, 2026 that it integrated J.P. Morgan Payments' new banking authorization service (BAS) API.
- The API replaces certificates from an external certification authority with an authorization the client signs, according to Embat.
- A single multi-tenant certificate connection at J.P. Morgan Payments covers multiple subsidiaries, so multi-entity groups do not repeat setup per legal entity.
- No pricing, volume or client-count figures were disclosed, so the commercial effect is unmeasured.
- Treasurers should test the claim that setup takes days by timing the first entity and the fifth.
Embat announced on Wednesday, Nov. 4, 2026 that it has integrated J.P. Morgan Payments' new banking authorization service API, letting joint clients connect J.P. Morgan accounts to Embat's treasury platform. The claim is about time to connect, not price: Embat says a process that took months now takes days. No fees, volumes or client numbers were disclosed, so the story is connectivity friction, not a new revenue line.
What changes in the connection
According to PYMNTS' account of the announcement, the old route required certificates from an external certification authority, plus extensive data validation and signatures. The new route has clients sign legal documents authorizing Embat to access their accounts, with no technical development. Embat co-founder and co-CEO Antonio Berga is quoted saying what used to take months is now operational within days. That timing is Embat's own claim and has not been independently measured.
Why multi-entity groups feel it most
The reported benefit is largest for groups with many legal entities. Embat says J.P. Morgan Payments' single multi-tenant certificate management connection covers multiple subsidiaries, so the connection is not rebuilt for each entity. Certificate work scales with entity count, so removing it per entity is where the time saving compounds. A single-entity company sees a smaller gain, since it only ever ran the old process once.
What the announcement does not show
Nothing in the reporting states pricing, adoption or the number of joint clients, so the commercial effect cannot be sized. Embat also says it is the first treasury management system to use J.P. Morgan Payments' own user interface through an API integration. That is a vendor statement, not a verified ranking. Embat has been building bank API connectivity for some time, having acquired Necto in February 2025, according to Tech.eu.
What treasurers should check
Lower onboarding friction also lowers the cost of moving between treasury platforms, which matters to anyone negotiating software fees. Treasurers should confirm which account types and payment functions the authorization covers, who holds the access grant, and how it is revoked. They should also time the first entity and a later one against the stated days. Until J.P. Morgan Payments or Embat publishes scope and terms, treat the saving as claimed, not demonstrated.
- What did Embat integrate with J.P. Morgan Payments?
- Embat integrated J.P. Morgan Payments' banking authorization service (BAS) API. Joint clients can link their J.P. Morgan accounts to Embat's treasury platform without IT development, according to Embat's Nov. 4, 2026 announcement as reported by PYMNTS.
- What does the BAS API replace?
- It replaces a setup that Embat says required certificates from an external certification authority, along with extensive data validation and signatures. Embat says that process can take months.
- Does the announcement disclose commercial terms?
- No. The reporting gives no fees, transaction volumes or client numbers. Any claim about revenue or market-share impact would be speculation.
- Embat Turns to J.P. Morgan for Better Bank-Treasury Connectivity — PYMNTS
- Embat acquires Necto to boost bank API connectivity and instant payments — Tech.eu
- Embedded Payments API overview — J.P. Morgan Payments Developer Portal