Stables has selected DFNS to power the wallet infrastructure behind its stablecoin payments platform. For a company whose entire product is moving money across borders, compliantly and reliably, the layer that holds keys, signs transactions, and enforces policy is the engine room. Settlement speed, transaction reliability, and the controls that satisfy regulators and partners all depend on it. By moving to DFNS, Stables is treating wallet infrastructure the way it treats the rest of its platform: as critical financial infrastructure that has to perform under real volume, not a dependency to be tolerated.
Stables, building the API to move money across Asia and MENA
Stables is developer infrastructure for stablecoin payments, built to move USDt across Asia and MENA. Its promise is simple to state and hard to deliver: one API to compliantly collect, convert, and move money anywhere. Where moving money across borders has traditionally meant stitching together five different banking vendors, Stables consolidates collection, conversion, settlement, and compliance into a single integration.
The platform is built around four building blocks: Virtual Accounts, reusable local payment details for collecting fiat and settling into stablecoins; Transfers, quote-first money movement across fiat rails, stablecoins, and supported corridors; Compliance, with KYC/KYB, sanctions screening, AML monitoring, and travel rule support built in; and AI Agents with an MCP server, letting AI assistants operate payments safely.
The scale behind it is real. Stables processes over $2 billion in annual USDt volume, supports 160+ markets, settles in under an hour on average, and operates to a 99.99% uptime SLA, with SOC 2 certification and a compliance stack spanning FATF travel rule and PCI-DSS. Just as important is how it is built. Stables is developer-first: clean REST APIs, a full OpenAPI spec, a sandbox environment, and documentation that lets a team integrate stablecoin payments in an afternoon, with no blockchain expertise required and new corridors added through configuration rather than new banking relationships.
That combination, deep compliance coverage, genuine cross-border reach, and an integration a developer can complete in a day, is why Stables has become trusted infrastructure for companies moving serious stablecoin volume. It is also exactly the kind of product whose success rests on the reliability and programmability of the layer underneath it.
Why Stables moved to DFNS
Stables previously ran on Fireblocks. The decision to migrate came down to the difference between infrastructure built dashboard-first and infrastructure built API-first, a difference that matters enormously for a company automating money movement at scale.
An API, not a dashboard with an API attached. Stables’ entire value proposition is programmatic: integrate once, automate everything, add corridors by configuration. DFNS was architected from day one as a programming interface, where every capability, wallet creation, transaction signing, policy enforcement, webhooks, recovery, is available over API, and the dashboard is simply another client of those same APIs. For a team that wants to build flows as code rather than toggle rules in a console, that architectural starting point is the whole game.
Reliability at payments scale. A failed payment is not a retry; it is a lost customer. DFNS runs its own blockchain node infrastructure, chain by chain, with API-level idempotency, transaction reindexing and rebroadcasting for stuck flows, and real-time failover, rather than depending on third-party RPCs. This is the same infrastructure that payment companies like Bridge, now part of Stripe, and Iron, now part of MoonPay, rely on for thousands of daily transactions across Ethereum, Solana, Base, Tron, and Polygon at near-zero failure rates, and that kept those clients’ transactions flowing through the Solana congestion crisis without manual re-signing or resubmitting. It is underpinned by KU25, our patent-pending MPC protocol for ECDSA, among the fastest in production. For a business settling USDt in under an hour across 160+ markets, that reliability is the product.
Pricing that scales with a payments business. DFNS pricing is transparent and usage-based, with no fees on assets under custody and no cut of transaction volume. We are a technology provider for financial institutions, not a financial institution. For a high-throughput payments company, a model that takes basis points or per-transaction fees works directly against unit economics. A predictable subscription does not.
A security model built for institutional money movement. DFNS separates authentication credentials from cryptographic key material, keeping keys in hardened, network-hosted environments rather than on end-user devices, in line with NIST guidance. Every mutating action is signed using WebAuthn and asymmetric cryptography, producing a verifiable audit trail of who did what, when, with a secret key DFNS never sees.
And the migration itself was manageable rather than the leap teams fear. Re-importing keys, policies, and signing rights is well-trodden work, and the result for Stables is a foundation that removes the ceilings it had started to hit, without giving up control of its funds for a moment in the process.
How DFNS supports Stables
DFNS provides an orchestration layer with a Wallet-as-a-Service platform built for institutional and enterprise use, delivering control, operational visibility, and consistent security across the entire wallet lifecycle. For Stables, wallets become governed financial objects rather than opaque cryptographic endpoints. Access rights, signing authority, and operational roles are defined and enforced at the infrastructure level, so wallet operations line up with the approval flows and controls Stables and its partners expect.
Policy-based execution applies thresholds, limits, and approval logic directly on live networks, without rebuilding controls at the application layer. The platform separates application logic from key management and signing, which reduces operational risk and simplifies the recurring security reviews and compliance audits a regulated payments business runs. Real-time webhooks feed reconciliation and reporting, keeping treasury and finance in sync. And the infrastructure scales across chains, assets, and transaction volumes without weakening control or audit guarantees, which matters for a platform expanding corridor by corridor.
By relying on DFNS for wallet infrastructure, Stables keeps its engineering focused on what differentiates its platform, virtual accounts, quote-first transfers, embedded compliance, and AI-operated payments, on top of a proven layer for key management, transaction execution, and resilience.
A practical foundation for stablecoin payments across Asia and MENA
Asia and MENA are among the most active regions in stablecoin payments today. Cross-border volume continues to grow, USDt is increasingly the settlement asset of choice, and regulators across these markets are formalising frameworks for stablecoins and digital payments in parallel. The companies that win in this environment will be the ones whose infrastructure holds up under real volume and regulatory scrutiny, not the ones retrofitting controls after launch.
Together, Stables and DFNS offer a deployment-ready foundation for that environment: focused on settlement speed, reliability, governance, and compliance rather than experimentation. As stablecoin rails continue to scale across Asia and MENA, the combination of Stables’ compliant money-movement platform and DFNS’ bank-grade wallet infrastructure gives the businesses building on Stables a base they can trust with production volume.
Start building on DFNS today: app.dfns.io/get-started
Frequently asked questions
What is Stables? Stables is developer infrastructure for stablecoin payments, built to move USDt across Asia and MENA through a single API to compliantly collect, convert, and move money. It is built around four building blocks: Virtual Accounts for collecting fiat and settling into stablecoins, Transfers for quote-first money movement, Compliance with KYC/KYB, sanctions screening, AML monitoring, and travel rule support, and AI Agents with an MCP server. Stables processes over $2 billion in annual USDt volume, supports 160+ markets, settles in under an hour on average, and operates to a 99.99% uptime SLA.
Who provides the wallet infrastructure behind Stables? DFNS powers the wallet infrastructure behind Stables’ stablecoin payments platform. DFNS provides a Wallet-as-a-Service platform built for institutional use, delivering key management, transaction execution, policy enforcement, and real-time webhooks across the wallet lifecycle. DFNS is a technology provider for financial institutions, not a financial institution itself — it charges no fees on assets under custody and takes no cut of transaction volume.
Why did Stables migrate from Fireblocks to DFNS? Stables previously ran on Fireblocks and moved to DFNS for infrastructure built API-first rather than dashboard-first. Every DFNS capability — wallet creation, transaction signing, policy enforcement, webhooks, recovery — is available over API, with the dashboard as just another client. Stables also cited reliability at payments scale, usage-based pricing with no fees on assets under custody or transaction volume, and a security model that separates authentication credentials from cryptographic key material.
How reliable is the infrastructure behind Stables? DFNS runs its own blockchain node infrastructure chain by chain, with API-level idempotency, transaction reindexing and rebroadcasting for stuck flows, and real-time failover rather than depending on third-party RPCs. The same infrastructure supports payment companies such as Bridge, now part of Stripe, and Iron, now part of MoonPay, and kept their transactions flowing through the Solana congestion crisis. It is underpinned by KU25, DFNS’ patent-pending MPC protocol for ECDSA.
Which networks does Stables run on? The infrastructure behind Stables processes transactions across Ethereum, Solana, Base, Tron, and Polygon, settling USDt in under an hour on average across 160+ markets.