How a new EMI actually gets a safeguarding account

Money that customers load onto an e-money product never becomes the institution's money. The framework requires EMIs to safeguard client funds, and the standard method is segregation: a dedicated account at a credit institution that holds customer funds separately from the EMI's own operating cash.

There is an alternative route under the framework - investing client funds in secure, liquid assets - but segregation at a credit institution is the standard method, and the one most new EMIs build their application around.

It is worth being precise about who safeguarding protects: the customers, not the institution. Segregation keeps client funds identifiable and apart from the EMI's own balance sheet, so the protection runs to the people whose money it is. That distinction matters later, because it shapes what a bank providing the account is actually taking on.

Safeguarding is not an operational detail to sort out after approval. Regulators assess safeguarding arrangements as part of the authorisation itself, and an EMI cannot launch without them. The application describes the arrangements concretely - which institution will hold the account, how it is structured, how client funds move in and out.

That creates the timing trap most licensing guides skip. The strongest applications name real arrangements with a real credit institution, but banks are slowest to commit to exactly the kind of client a pre-licence EMI is: no licence yet, no history, no volumes. Treat the safeguarding account as a workstream that starts on day one of the application, not a form to fill in once the regulator says yes.

Seen from the bank's side of the table, a new EMI is a concentrated parcel of other people's AML risk. Every customer the EMI onboards becomes, indirectly, the bank's exposure - and a new institution brings that exposure with no operating history to underwrite it. A promising founding team and a pending application are not a track record.

What moves a hesitant bank is not persuasion but a file that answers its risk questions before they are asked. In our experience, four documents do most of the work.

The instinct is to pick the friendliest bank and put everything into that one relationship. The problem is control: a bank can slow down or decline at any point, and a sequential approach means each refusal restarts the banking clock while the regulator's review keeps moving. Safeguarding is one of the classic ways an authorisation timeline stretches - we cover the wider pattern in our guide to EMI authorisation timelines.

Parallel candidates change the shape of the risk. No single decline is fatal, comparable term sheets give you an honest picture of the market, and the workstream keeps pace with the application instead of trailing it. This is stage four of how a SKY7 mandate runs: banking treated as a licensing workstream, with the same discipline as the application itself.

Jurisdiction choice changes the banking conversation. In Lithuania, licensed EMIs can access CENTROlink, the Bank of Lithuania's payment infrastructure - one reason the jurisdiction remains popular with e-money founders as of July 2026.

The caveat: access is not automatic. CENTROlink is available to institutions that meet the Bank of Lithuania's conditions, and those conditions are assessed on the institution's own merits - the licence opens the conversation, it does not end it.

If acquiring an existing licensed institution is on the table instead of building one, the catalogue of licensed companies currently listed shows what is available to buy rather than build.