Anyone offering accounts, cards or payments needs a regulatory basis. There are essentially two routes, they differ widely in effort, speed and control.
You apply for your own license as a payment (PI) or e-money institution (EMI) with the competent supervisory authority. That means: capital requirements, a robust compliance and risk team, audits, and an application process that realistically takes twelve to eighteen months.
For whom? For companies where the financial infrastructure itself is the core product and that need maximum control. The price for that is time, capital and ongoing regulatory effort.
Here a regulated partner institution holds the license, a technology partner supplies the software, and you bring the brand and customers. The product runs entirely under your name, and the institution carries the regulatory responsibility. This way you're live in weeks instead of years, without becoming an institution yourself.
EMAS Solutions supplies the software platform; regulated payment and e-money services run via a regulated partner institution. You offer account, card and app under your brand, license and supervision stay with the institution, the customer relationship with you.
Your own license means maximum control, but years and a team of your own. Via a partner institution you're live in weeks, without becoming an institution yourself, the license stays with the partner.
This article offers general technical context and is no substitute for legal or investment advice. The specific regulatory setup is structured individually per market and program.
Why 'trading in real time' isn't a question of app speed, but depends on whether the customer's money is already in the account.
Embedded finance brings accounts, cards and payments right to where your customers already are: into your product. What's behind it and where it pays off.
Three acronyms that come up in every embedded finance project, explained briefly, without a law degree.
The build-vs-buy question decides months, budget and team. When each path pays off.
Why gold, silver & co. in your own app are more than a niche feature, and how to embed them.
How dealers and brands offer a digital gold savings plan in their own app: fractional buys, automation and recurring revenue.
How dealers digitise scrap-gold buyback: transparent valuation, real-time payout to the customer's IBAN account, no cash, with more trust.
Precious-metal storage explained simply: customs warehouse, segregation, insurance and allocated storage, what brands should know and tell their customers.
Allocated vs. unallocated gold decides who legally owns the metal in the vault and what happens in insolvency. A guide for app providers and their customers.
Anyone wanting to launch their own gold app needs technology, regulatory access, storage and payments. This guide shows what is really required and why build-vs-buy comes down in favour of a managed solution.
The metal-to-metal swap and savings plans turn one-off purchases into ongoing revenue. How swaps work with a transparent spread and no euro detour, and how they retain customers.
Setup, platform licence, revenue share, card and compliance costs: we show how the price of a white-label finance app really breaks down and why a single headline figure is misleading.
Three terms that are constantly confused. We cleanly separate Embedded Finance, embedded finance and white-label, with examples and the question of when each approach fits.
Dedicated IBANs for your customers without becoming a regulated institution yourself. We explain the route via a regulated partner institution, the difference between dedicated and shared IBANs, and the topic of safeguarding.
How brands, fintechs and platforms issue virtual and physical Visa cards under their own branding, without holding a licence themselves.
How a business earns money by issuing its own cards and embedding finance, interchange, revenue-share and which flows become income.
Tell us about your project, no obligation. We usually reply within a few hours on business days.