Predictable JSON, clear error semantics.
PMM draft · copy NOT yet MLRO-reviewed · carries draft annotations · ## no product notes implemented yet ##
FCA-authorised EMI
FRN 901043
Build on DigiDoe.
For developers integrating with DigiDoe: e-money accounts, payments and FX, with KYC/KYB and payment rails built in.sub-line rebuilt for the e-money glossary (R3) and drops the "under our licence" framing (R81), needs MLRO
FCA-authorised EMI · FRN 901043 · API access is subject to onboarding, eligibility and compliance approval.
One integration, your supported workflows.heading form derived from R88, needs MLRO
One REST API for supported onboarding, account, payment, FX and transaction workflows. Subject to eligibility, onboarding and compliance checks.
EEA rail reference removed from the pill diagram, ruling R82: DigiDoe cannot currently open EEA accounts. Removed . R82, no safer alternative fits a pill label
Endpoint counts in the code window verified against guide.digidoe.com on 2026-08-17 (all seven match); the live docs also list Contact and TransactionInformationRequests, which the illustration omits. Flagged . R92, incomplete against the live reference
FCA-authorised, ISO-certified, relevant funds safeguarded.
Stated once, here, with the limits included.
Electronic Money Institution, FRN 901043
Authorised by the Financial Conduct Authority. DigiDoe is not a bank. Check the Register, or read the guidance on using payment service providers.
ISO 27001 and ISO 22301 certified
Certified for information security and for business continuity by British Assessment Bureau, a UKAS-accredited certification body.
Safeguarded, not FSCS-protected
Relevant funds are safeguarded in accordance with applicable regulatory requirements and are not protected by the FSCS.
How relevant funds are safeguarded
Payments are screened against sanctions and financial-crime controls, and transactions are monitored. These controls reduce risk; they do not remove it.
The API console, before you write a line
Explore requests and responses in a console designed to make integration boring, in the best way.
screenshot must be demo data only, names and amounts masked before publishTest supported API workflows using synthetic sandbox data before requesting production access.
Receive webhook notifications for supported account events, subject to the delivery and retry behaviour described in the API documentation.
Sandbox card uses R85's supplied wording; webhook card uses R95's, and its delivery/retry behaviour is still awaiting Dmitrii's confirmation per R95's own compliance-handling note. Flagged . R95 sign-off open
The API documentation is live.
Full endpoint reference for the DD PublicAPI for EMx, plus the EMx authorisation and onboarding flows. Sandbox and API-console access are available to eligible integration partners on request.
Read the API docs
Request sandbox access
DigiDoe's regulated infrastructure →
CTA label reworded from R81's safer alternative, needs MLRO
