A company is close to switching payment providers when its regulatory status, its markets or its payments team changes. Watch for a new licence or authorisation on a public register, a new rule on how it safeguards client money, a first payments hire, and a launch in a new country or currency. Each forces a review of the current provider.
Why do these events trigger a switch?
A payment provider gets chosen once, when the company is small, and then nobody reopens the decision until something breaks or something changes. Switching costs engineering time and puts revenue at risk, so the review needs a reason with a date on it. The signals below give one.
| Signal | What it forces | Where to see it | Who to contact |
|---|---|---|---|
| New authorisation on a regulator's register | New fiat rails, bank accounts, safeguarding and reporting for the licensed entity | ESMA interim MiCA register, the FCA register, national registers | CFO, head of payments, compliance officer |
| A safeguarding or reporting rule change | A review of safeguarding banks and reconciliation tools | Regulator policy statements | CFO, head of finance operations |
| First payments engineering or payments operations hire | A new owner who will audit the current setup | Careers page, job boards | Head of payments, or the hiring manager named in the post |
| Launch in a new country or currency | Local acquiring, local payouts, a new currency account | Press releases, product changelogs, app store listings | Head of payments, VP product |
| Fundraise with expansion named as the use of funds | Budget for the launch above | Funding announcements | CFO, COO |
| Provider event: account closure, price rise, outage | An urgent search | Status pages, customer forums, the company's own posts | CTO, head of payments |
The first two rows are the most precise, because a regulator dates them and names the entity.
What does the MiCA register show right now?
It shows a wave of newly authorised firms that need fiat payment rails. ESMA publishes the interim MiCA register as CSV files and updates it weekly (ESMA, October 2026). Firms could keep operating under national rules until 1 July 2026 or until they were granted or refused authorisation, whichever came first.
We counted the crypto-asset service provider file as ESMA last updated it on 7 October 2026 (our data, October 2026). It lists 370 entries. Of those, 166 are authorised to exchange crypto-assets for funds, which means they move fiat money and need banking and payment partners. Germany is the home member state for 103 entries.
Authorisations by quarter, from the same file:
| Quarter | Authorisations |
|---|---|
| Q4 2024 | 4 |
| Q1 2025 | 12 |
| Q2 2025 | 27 |
| Q3 2025 | 26 |
| Q4 2025 | 83 |
| Q1 2026 | 36 |
| Q2 2026 | 106 |
| Q3 2026 | 67 |
| Q4 2026, to 7 October | 7 |
June 2026 alone had 76, the month before the transition period ended. Method: we grouped entries by their authorisation date. One entry carries a date in 2028, which looks like a data entry error, and one has no date; we left both out of the quarterly table. Three entries show an end date for their authorisation.
For a payments company, each new line is a firm that has just changed its legal status. Its bank, its safeguarding setup and its payout provider may not have been chosen for a licensed entity, and the compliance team now has a regulator asking about each of them.
What changed for UK payment and e-money firms?
The FCA's new safeguarding rules came into force on 7 May 2026. They require monthly reporting, annual audits for firms holding £100,000 or more in client funds, daily checks and better failure planning (FCA, 7 August 2025). The FCA found that payment firms that failed between Q1 2018 and Q2 2023 had average shortfalls of 65% of their customers' funds.
That rule change sends UK payment and e-money institutions back to their safeguarding banks and their reconciliation tools. Firms that run daily reconciliation by hand now have a monthly regulatory return that depends on it. Vendors of safeguarding accounts, reconciliation software and audit preparation have a dated reason to call.
How do you avoid acting on the wrong company?
Match each signal to exactly one legal entity before you write. A hiring or funding headline usually names a brand, while the register names a legal entity. We caught a hiring signal for a spend management company that our tools matched to a crypto payments company with the same first word; the full case is in which buying signals predict a B2B purchase.
Use these checks:
- Use the legal entity identifier. The MiCA file lists an LEI for each firm. Match on it, then find the trading name and website.
- Check the website field against the domain you will email. The register lists a website for each entry.
- Confirm the service code. A firm authorised only for custody has different payment needs from one that exchanges crypto for funds.
- Find the group. Large groups register several entities. Write to the group's payments owner once, not to each entity.
How fast should you act on a register entry?
Act in the week the entry appears. A firm that has just been authorised is setting up the accounts and providers it will run on for years. Once those contracts are signed, the next review usually waits for the next change in status or markets.
Pull the ESMA file on a fixed day each week, compare it with last week's copy, and keep only the new rows. Do the same with the FCA register for the firm types you serve.
A decision rule for payment switching signals
- Act on any new authorisation that includes a service moving fiat money.
- For a rule change with a date, contact the finance owner before that date.
- Add weight when two signals hit the same company within a quarter, such as an authorisation and a payments hire.
- Drop any signal you cannot match to one legal entity and one domain.
- Contact the owner named in the table, with the signal and its date in the first line.
To set up register monitoring for your segment and turn new entries into a weekly target list, start with The Diagnostic at $2,500.