Notifications
Clear all
Topic starter
25/06/2026 1:15 am
TL;DR: Embedded finance is projected to grow from nearly $2.6 trillion in U.S. transactions in 2021 to more than $7 trillion by 2026, while global revenues are forecast to reach $348.8 billion by 2029, according to Ping Identity; the access model behind that growth is still the bottleneck. Secure third-party governance, not product integration, now determines whether embedded finance scales without exposing identity and compliance risk.
NHIMG editorial — based on content published by Ping Identity: digital identity for embedded finance and secure third-party access
By the numbers:
- Embedded finance accounted for nearly $2.6 trillion of total financial transactions in the U.S. in 2021.
- By 2026, that figure is expected to nearly triple, exceeding $7 trillion and making up more than 10% of all U.S. financial transactions.
- In Europe, embedded finance revenues could surpass €100 billion by the end of the decade.
Questions worth separating out
Q: How should teams govern third-party access in embedded finance platforms?
A: Treat each third party as a governed identity relationship, not just a technical integration.
Q: Why do embedded finance programs expose IAM weaknesses so quickly?
A: Because they multiply trust relationships across organisations that do not share the same control model.
Q: What breaks when third-party access is onboarded manually?
A: Manual onboarding usually creates inconsistent entitlements, duplicate accounts, and unclear ownership of access decisions.
Practitioner guidance
- Map third-party identities by business relationship Create an inventory of every external party that can initiate, approve, or influence embedded finance workflows.
- Replace manual partner onboarding with policy-driven lifecycle steps Automate approval, entitlement assignment, recertification, and revocation for partners that support embedded financial journeys.
- Tie access scope to transaction purpose Limit third-party permissions to the minimum set needed for the specific embedded use case and expire them when the use case changes.
What's in the full article
Ping Identity's full article covers the operational detail this post intentionally leaves for the source:
- Examples of embedded finance use cases across payments, lending, insurance, wealth, and identity verification.
- The business framing for why third-party access is the bottleneck to scaling embedded financial services.
- How digital identity is positioned as the mechanism for extending secure access across B2B, B2B2C, and B2B2X relationships.
- The product and ecosystem context behind Ping Identity's embedded finance eBook.
👉 Read Ping Identity's article on digital identity for embedded finance →
Embedded finance and third-party access , where IAM breaks down?
Explore further
25/06/2026 10:32 am
Embedded finance is not mainly a product integration problem, it is a third-party identity governance problem. The article correctly frames growth as dependent on secure access, but the real constraint is whether organisations can model partners as governed identities rather than ad hoc integrations. Once a business relationship requires repeated access across systems, IAM, IGA, and PAM controls all become part of the delivery path. The practitioner conclusion is that embedded finance scales only when partner identity is treated as core infrastructure.
A few things that frame the scale:
- Two-thirds of enterprises have endured a successful cyberattack resulting from compromised non-human identities, with a quarter encountering multiple attacks, according to The 2024 ESG Report: Managing Non-Human Identities.
- The average organisation believes more than 1 in 5 of their non-human identities are insufficiently secured, which shows how governance gaps accumulate before a breach is visible.
A question worth separating out:
Q: What frameworks help align embedded finance access with governance requirements?
A: A strong approach combines NIST Cybersecurity Framework 2.0 for governance and risk management with identity lifecycle controls that support certification, revocation, and evidence collection. The practical test is whether you can prove who has access, why they have it, and how quickly that access can be removed when the relationship changes.
👉 Read our full editorial: Embedded finance and third-party access: the identity governance gap
