EUR/GBP Virtual Account Migration

Migration context

Due to a requirement from our banking partner in line with the new MiCA regulation, we need to migrate all EUR and GBP services from our Bulgarian entity – Due Payments EOOD – to our Spanish MiCA-licensed entity, Due Network S.L., by May 27th EoD at the latest.

What is changing

Rail	What changes	What this means for you
EUR	Minor change - Integration stays the same:	*From May 14: All new EUR VAs are issued under Due Network S.L. via ClearBank as the underlying bank. Same API, same flow — just a different account name and underlying bank. Existing EUR VAs (created up to May 14)*: Stay live until May 27, then must be migrated. You need to swap the old account details for the new Due Network S.L. ones and notify affected users by May 27, although you can start doing it from May 14 already.
GBP	Breaking change - We move away from static details to dynamic ones	From May 27: static GBP virtual accounts go away, and the underlying bank changes to RBS (The Royal Bank of Scotland). Named GBP VAs return end of Q2 once the new provider is integrated. In the meantime, every GBP deposit must be created dynamically via POST `_/v1/transfers_`. Each call returns one-time deposit instructions: sort code, account number, memo, exact amount, and an expiry. Rules for users: exact amount + exact memo + before expiry. No reusing old memos. If any of those are off, the deposit may not auto-allocate.
Pay-outs	Name change on both rails	*From May 27*: EUR and GBP payouts will go out under Due Network S.L. instead of Due Payments EOOD. No integration change, but the sender name your users' counterparties see will be different.

Rail

What changes

What this means for you

EUR

Minor change - Integration stays the same:

From May 14: All new EUR VAs are issued under Due Network S.L. via ClearBank as the underlying bank. Same API, same flow — just a different account name and underlying bank.
Existing EUR VAs (created up to May 14): Stay live until May 27, then must be migrated. You need to swap the old account details for the new Due Network S.L. ones and notify affected users by May 27, although you can start doing it from May 14 already.

GBP

Breaking change - We move away from static details to dynamic ones

From May 27: static GBP virtual accounts go away, and the underlying bank changes to RBS (The Royal Bank of Scotland). Named GBP VAs return end of Q2 once the new provider is integrated.

In the meantime, every GBP deposit must be created dynamically via POST _/v1/transfers_. Each call returns one-time deposit instructions: sort code, account number, memo, exact amount, and an expiry.

Rules for users: exact amount + exact memo + before expiry. No reusing old memos. If any of those are off, the deposit may not auto-allocate.

Pay-outs

Name change on both rails

From May 27: EUR and GBP payouts will go out under Due Network S.L. instead of Due Payments EOOD. No integration change, but the sender name your users' counterparties see will be different.

Migration flow - Key dates

May 14, 2026 — new EUR VAs start being issued under Due Network S.L.
May 27, 2026 — deadline for migration of existing EUR VAs; GBP switches to dynamic deposits.
End of Q2 2026 (expected) — GBP VAs return.

Platform action list

EUR

Continue using the existing EUR virtual account creation integration.
Identify existing EUR virtual accounts created up to May 14.
Notify affected users that their existing EUR virtual account details will be migrated on May 27.
Replace old EUR account details with the new Due Network S.L. account details after migration.
Check the status of VAs you render for clients

GBP

Stop presenting GBP virtual account details (static) after the migration cutover
Call POST /v1/transfers per deposit.
Display the returned sort code, account number, memo, amount, and expiry.
Tell users: exact amount, exact memo, before expiry. Never reuse.

For GBP dynamic deposits, the memo/reference is mandatory and changes for each transfer. If the sender omits or changes the memo, sends a different amount, reuses old instructions, or sends funds after the transfer expires, Due may not be able to automatically allocate the deposit.

Summary

EUR and GBP rails are being migrated to Due´s MiCA regulated entity on May 27, so:

From May 14, new EUR virtual accounts are created through ClearBank under Due Network S.L. The integration stays the same, and existing EUR accounts created before May 14 migrate on May 27.
From May 27, GBP platforms must use dynamic per-deposit transfer instructions created through POST /v1/transfers, with RBS (The Royal Bank of Scotland) as the underlying bank. This is a breaking change if you use GBP.