Accounts, payments, and FX in one surface
One integration delivers programmatic access to multi-currency accounts, payment initiation across SEPA/FPS/SWIFT, FX conversion, and payee management — no separate providers.
‘Xace’ and ‘Xace Europe’ are trading names of Xace Limited and Xace Malta Ltd. Xace Limited is a private limited company (number 11742963) registered in England and Wales. Xace Malta Ltd is a private limited company (C 102626) registered at Level 5, Carolina Court, Giuseppe Cali Street Malta XBX 1425.
Xace Limited is regulated by the Financial Conduct Authority, FRN 948213, under the Payment Services Regulations 2017 as an Authorised Payment Institution, providing payment accounts.
Xace Malta Ltd is licensed and regulated by the Malta Financial Services Authority to undertake the business of a payment services in terms of the Financial Institutions Act.
Xace Limited is a registered EMD agent of Modulr FS Limited, a company registered in England and Wales with company number 09897919, which is authorised and regulated by the Financial Conduct Authority as an Electronic Money Institution (Firm Reference Number: 900573) for the issuance of electronic money and payment services. Your account and related payment services are provided by Modulr FS Limited. Whilst Electronic Money products are not covered by the Financial Services Compensation Scheme (FSCS) your funds will be held in one or more segregated accounts and the full value safeguarded in line with the Electronic Money Regulations 2011 – for more information please see follow this link.
Xace Limited is also a partner of Modulr Finance B.V., a company registered in the Netherlands with company number 81852401, which is authorised and regulated by the Dutch Central Bank (DNB) as an Electronic Money Institution (Firm Reference Number: R182870) for the issuance of electronic money and payment services. Your account and related payment services are provided by Modulr Finance B.V. Your funds will be held in one or more segregated accounts and the full value safeguarded in line with the Financial Supervision Act (Wet op het Financieel Toezicht, Wft) – for more information please follow this link.
Xace Limited also provides other Payment Services under its own licence. These are separate and unrelated to the account and payment services you receive from Modulr FS Limited.
Your card is issued by Modulr FS Limited or Modulr Finance B.V. pursuant to their respective license by Visa Europe. Visa and the Visa brand mark are registered trademarks of Visa Europe.
Xace API
Embed accounts, payments, FX, and approvals straight into your product—on infrastructure trusted by iGaming leaders and built for regulated scale.
REST · OAuth 2.0 · Real-time webhooks
API coverage
Every banking primitive accessible from a single integration point. No separate providers, no undocumented endpoints, no surprises at scale.
Accounts, payments, FX, payees, and approval controls across consistent REST endpoints. Versioned contracts, idempotency keys on writes, and predictable error handling at every primitive.
Subscribe to granular account and payment events. Automatic retry with exponential backoff and full delivery logs keep your integration in sync without polling.
Mirrors production exactly — same endpoints, same auth schema, simulated rails. Your integration is proven before it touches live money.
Accounts, payments, FX, Open Banking, and approval controls as clean REST endpoints. Consistent patterns, versioned contracts, idempotency on every write operation.
One integration delivers programmatic access to multi-currency accounts, payment initiation across SEPA/FPS/SWIFT, FX conversion, and payee management — no separate providers.
Consistent JSON structure, explicit error codes, idempotency keys on all write operations, and cursor pagination — so your integration behaves as expected at scale.
Granular permission scopes let every API client hold exactly the access it needs. Server-to-server and user-delegated flows both supported from the same credential model.
Authentication
OAuth 2.0 with granular permission scopes means every API client holds exactly the access it needs — nothing more. Server-to-server flows handle backend integrations; user-delegated flows support multi-tenant architectures where users grant scoped access to their own accounts. JWT Bearer tokens rotate automatically, and every authentication event is logged and auditable from the developer dashboard.
Rate limits
Generous per-method rate limits with standard response headers let your integration plan around capacity rather than react to failures. Burst allowances handle high-volume payment windows — bulk payroll runs, affiliate batch payouts, FX conversion cycles — without surprises. Rate limit status surfaces in every response, so your system degrades gracefully when headroom narrows rather than silently failing at the worst moment.
Batch operations
Batch endpoints across payments, payee creation, and FX conversions handle high-volume flows in single API calls. Idempotency keys are supported on every batch operation — retries are safe by default, with no duplicate payments and no partial-failure risk left unresolved. Batch results return per-item status so your system handles the minority of exceptions without reprocessing the entire set.
Built for evaluators
Most banking APIs are designed for getting-started guides — not the technical questions that matter when a product team commits to an integration. What does the rate limit look like at a hundred thousand payments a month? How does the auth model handle a multi-tenant architecture? What happens to a webhook when it fails three consecutive deliveries?
Xace API documentation covers those questions directly — with accurate reference docs, reproducible sandbox scenarios, and a technical contact who knows the integration from the inside. The goal is that your engineering team has real confidence before the first production call, not after the integration is already serving customers.
Technical questions
Answers for product and engineering teams validating API coverage, authentication, rate limits, and sandbox depth.
Yes—full-fidelity simulation for accounts, payments, FX, and approvals. Build and test end-to-end flows before going live.
Yes—use your domain, branding, and workflows with Xace infrastructure. The white-label experience covers web apps, admin panels, and client-facing communications.
Through Salt Edge connectivity for AISP/PISP access. You can pull balances, transactions, and initiate payments programmatically.
Natively—brands, regions, and role-based access are first-class. The API is built for complex organisational structures from the ground up.
Yes—partner announcements, marketplace listings, and joint case studies are available. We work with integration partners on go-to-market strategy.
Where next
Keep building
The on-site developer landing that bridges marketing into the developer portal.
Open the docs →Evaluation support
Everything you need to assess fit with confidence
Compare the platform against your operating model, governance needs, and rollout priorities before committing.
We will map the platform to your structure, priorities, and implementation route.
Response during business hours from the Xace team.