Category: stablecoin payments infrastructure / virtual-account and payout control plane / compliance-heavy developer platform
Summary: Stables is best understood as a compliance-heavy stablecoin payments control plane for fintechs, payment platforms, and other operators that need programmable movement between fiat rails and digital assets. The strongest signal in this pass was the official docs corpus and llms surfaces, which jointly expose customer onboarding, KYC/KYB and entitlement workflows, quotes, off-ramp transfers, virtual accounts, webhooks, sandbox access, and an agent-facing MCP server. That combination makes Stables look broader than a simple on/off-ramp or payout API: it is packaging customer compliance, money movement, and bank-detail issuance into one developer surface.
What it does:
Lets developers create individual and business customers, request entitlements, and submit KYC/KYB data before a user can transact
Provides quote and transfer APIs for moving between supported stablecoins or digital assets and fiat rails, with current quickstart emphasis on crypto-to-fiat off-ramp flows
Issues virtual accounts with local bank details in currencies like USD, EUR, and AUD for user deposit and payout workflows
Exposes webhook subscriptions so integrators can receive customer, KYC, and payment-status events in real time
Offers a sandbox environment for testing integrations before moving real funds
Publishes an MCP server so AI agents can manage customers, quotes, transfers, virtual accounts, API keys, and webhooks programmatically
Key claims:
The docs homepage frames Stables as a platform to “Build compliant stablecoin payments infrastructure” with “APIs and tools for developers and agents to move money globally - securely and at scale”
The welcome and quickstart docs position Stables as “the infrastructure layer for stablecoin-powered payments” and say developers can send and receive payments while issuing USD, EUR, and AUD virtual accounts with local bank details
The customer quickstart says every action is tied to a Stables customer and that users need entitlements plus KYC/KYB data before they can transact
The transfer quickstart says the Transfer API supports conversion between supported fiat and cryptocurrency currencies and that the currently documented production flow is crypto-to-fiat off-ramp, while directing stablecoin receipt and payout use cases toward Virtual Accounts
The webhook guide documents subscription creation, event-type selection, signature verification with HMAC-SHA256, and idempotent event handling using event IDs
The sandbox guide says the sandbox base URL is https://api.sandbox.stables.money and notes the sandbox is functional for customer creation and KYC testing
The docs llms.txt enumerates first-party surfaces across customers, identity verification, entitlements, compliance restrictions, transfers, virtual-account whitelisting, limits, fees, API keys, and webhooks
The official MCP server README says Stables exposes 25 tools across customer management, quotes, transfers, virtual accounts, API keys, webhooks, and notifications for AI-agent workflows
Whitepaper: No canonical standalone Stables whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official docs corpus, llms.txt / llms-full.txt, and the first-party MCP server repository; see ../whitepapers/stables-primary-sources-2026-04-30.md.