# Stable > Stable is an ecosystem covering the full money cycle: multi-currency accounts and > cards, buying and selling crypto with fiat, and non-custodial stablecoin swaps > across chains. One part of it is programmable today — the Stable Swap API, a public > HTTP API for single-chain swaps (stablecoin to stablecoin inside one chain) and > cross-chain swaps (atomic swap between two chains) on Ethereum, Solana, BNB Smart > Chain, Tron and Polygon. It needs no credentials. The full text of Stable's key pages and first-party facts, for AI agents. Sections with a "Source:" line come from that page — cite it. Sections without one are facts maintained by Stable, current as of their "Updated:" date — cite the source given next to each fact, or this file. Buying and selling crypto for fiat runs through a widget on stable.com, not an API, and accounts and cards are opened in the product itself — neither has public developer documentation. If you are integrating with Stable programmatically, you are integrating with the swap API described here. **Company and licences.** Stable.com is a brand of the Unlimit group: 17+ years on the market, 17 global offices, 50,000+ enterprise partners worldwide. Unlimit EU Ltd (Cyprus, HE328641) is an Electronic Money Institution licensed by the Central Bank of Cyprus (authorisation 115.1.3.7). Unlimit Crypto Limited (Cyprus, HE437355) is authorised by the Cyprus Securities and Exchange Commission as a Crypto-Asset Service Provider under MiCA, Regulation (EU) 2023/1114. In the United Kingdom, Stable.com is a trading name of Unlimit UK Ltd, authorised by the Financial Conduct Authority as an Electronic Money Institution (FRN 978706). Unlimit also holds local licences in 13 markets: Brazil, Mexico, Colombia, Peru, Uruguay, Nigeria, Kenya, Tanzania, Indonesia, India, Hong Kong, the UK and Europe. A licence in a market does not mean every product is offered there — see the coverage page below. **The widget.** stable.com has Swap, Buy, Sell and Bank tabs and works with your own self-custody wallet. Buying and selling have no exchange fees, only a processing fee; swaps have no slippage and no hidden markups. Visitors in the United Kingdom get none of the widgets. Supported chains, stablecoins, fiat currencies, countries and wallets are listed on the coverage page below. Start with the OpenAPI spec if you are calling the API: it is the machine-readable contract for every endpoint, with schemas and captured examples. Read the integration guide for the parts a contract cannot carry — the order of calls, the difference between gasless and self-paid swaps, and the EIP-712 payloads you have to sign. **The swap is non-custodial and every swap is checked.** The backend runs an AML check and issues a maintainer signature per swap, carrying its own nonce and a short deadline, so an order cannot be replayed or assembled without us. Fiat-backed stablecoins only — no DAI, nothing algorithmic. **Rates and fees.** The rate is fixed and independent of market price or a depeg. The protocol fee is charged in the source token, is configured per token and per direction, and only passes on the cost charged by the stablecoin issuers — several pairs are set to 0% both ways, and moving one and the same token between chains is always free. The same pair can cost differently in each direction, so do not assume a rate: read `tokenFee` from the quote. On-chain gas is always paid by the user, in the swapped token or in the chain's native currency. **Cross-chain swaps are atomic.** If the swap does not complete, your tokens are refunded automatically; a partial swap is impossible by design. Live chain and asset data is better read from the API than from any document — the catalogue endpoint is listed under API below. **Try it — copy-paste-runnable, no credentials:** - List every supported chain and asset: `curl https://api-defi.stable.com/openapi/swap/config/all` - Quote 1500 USDC to USDT on BNB Smart Chain: `curl -X POST https://api-defi.stable.com/openapi/swap/status -H 'Content-Type: application/json' -d '{"chainFrom":"103","assetFrom":"USDC","chainTo":"103","assetTo":"USDT","amountFrom":"1500"}'` - Chain ids are `101` Ethereum, `102` Solana, `103` BNB Smart Chain, `104` Tron, `106` Polygon. These are internal ids, not EVM chain ids — the `chainId` inside an EIP-712 payload is the real EVM one (`1`, `56`, `137`), which the API does not report anywhere. Ask us for it. - The quote carries `min` and `max` for that asset on that chain. Respect them: a quote below `min` still returns, but the order will not. ## Pages - [Home](https://stable.com/index.md): The front page: the account offer, the swap, buy, sell and bank widgets, which of them a visitor's region gets, and who provides the service - [FAQ](https://stable.com/faq.md): Which Unlimit entity provides each Stable.com service and under which licence. Not shown to visitors in the United Kingdom - [Customer terms and information](https://stable.com/legal-documents.md): Terms and conditions, fee schedules and customer policies as PDFs, for EU and for UK customers - [Privacy Centre](https://stable.com/privacy-centre.md): Personal data commitments, the privacy notices that apply to each product, and how to reach the data protection team - [Stable.com at TOKEN2049 Singapore](https://stable.com/token-2049.md): Event page: the business account, cash in / move / cash out across fiat and stablecoins, press coverage and meeting booking - [Networks, assets, currencies and countries](https://stable.com/coverage.md): What the swap, buy and sell widgets support: chains and stablecoins, fiat currencies, countries and wallets, as a snapshot of the live config APIs - [Everything in one file](https://stable.com/llms-full.txt): This file, every page above, the business account overview and the swap API integration guide, concatenated ## Documentation - [Stable Swap API integration guide](https://stable.com/docs/stable-swap-api.txt): Endpoints field by field, flows for single-chain and cross-chain swaps, gasless and self-paid, EIP-712 signing rules and error handling ## API - [OpenAPI specification](https://stable.com/openapi.json): OpenAPI 3.1 contract for the swap API — every operation with schemas and captured examples - [Chain and asset catalogue](https://api-defi.stable.com/openapi/swap/config/all): Live JSON listing every supported chain and the assets available on it, with token addresses and decimals - [MCP server](https://api-defi.stable.com/v1/mcp): Model Context Protocol endpoint exposing read-only tools for swap configuration, quotes, order status, account balances and allowances ## Optional - [Stable](https://stable.com): Product site --- Updated: 2026-10-26 # Stable.com for business The global account for the stablecoin era: a full-service financial platform that brings traditional and digital finance together. - 17 global offices - 17+ years on the market - 50,000+ enterprise partners worldwide - Licensed and regulated: EU and UK Electronic Money Institution (EMI), EU MiCA Opening an account: [onboarding-kyx.stable.com](https://onboarding-kyx.stable.com/auth). Accounts and partnerships: [partnerships.accounts@stable.com](mailto:partnerships.accounts@stable.com). Support: [accounts.support@stable.com](mailto:accounts.support@stable.com). ## Global accounts 1. **One global account with local details.** Multi-currency accounts for companies incorporated across Europe, the UK, APAC, LATAM and Africa, including Singapore, Hong Kong, the USA and many more. 2. **Employee and freelancer accounts.** Set up accounts for employees and freelancers in minutes, and pay everyone from one place. 3. **Pay and get paid globally.** Transfers to 120+ countries at low cost via SEPA, SEPA Instant, TARGET2 and TIPS ( EUR), ACH (USD), SWIFT and more. Collect from customers in their preferred currency without unnecessary conversion fees. 4. **Fully digital onboarding.** No branch visits required. 5. **Dedicated relationship manager and support.** A named contact for your account, backed by the support team. 6. **Payment cards.** Free virtual payment cards, Apple Pay and Google Pay compatible, plus physical cards accepted worldwide. 7. **Get paid your way.** Payment links, global card acquiring and 1,000+ local and global payment methods, available through Unlimit. 8. **Fits into the accounting stack.** Integrations with QuickBooks and Xero. ## Stablecoins and digital assets - **Buy, sell and swap stablecoins.** Buy with fiat and cash out to the currency of your choice for a minimal processing fee. Swap across chains gasless, with the lowest protocol fee and no slippage. - **Decentralised finance.** Non-custodial access across multiple blockchain stablecoin networks. Coming soon: - **Lending protocol** — borrow stablecoins against BTC or ETH. - **Stock tokenisation** — access tokenised stocks on-chain. ## Card acquiring and licences - Principal member of Visa, Mastercard, UnionPay, JCB, Discover, Diners Club, Elo and American Express. - Local licences in 13 markets: Brazil, Mexico, Colombia, Nigeria, Kenya, Uruguay, Indonesia, Hong Kong, Tanzania, Europe, the UK, Peru and India. - A suite of 1,000+ local and global payment methods across Europe, Africa, LATAM, APAC and India. ## Industries supported Artificial intelligence; blockchain and Web3; digital services; online marketing; physical goods and retail; video games and mobile apps; trading and financial services; media and entertainment; technology and IT; software and SaaS; e-commerce; affiliate marketing; social networks and platforms; and many other business sectors. --- Source: https://stable.com/index.md # CAN YOUR BANK DO THAT? One payment account for 180 countries and 150 currencies. Send, spend and convert like a local — wherever you are. Cards and DeFi included. Free transfers. [Open an account](https://onboarding-kyx.stable.com/auth) — It takes a few minutes. > Page: https://stable.com/. The page is the same everywhere except for the widget below the offer, which depends on the > visitor's location. ## Widgets Below the account offer, the page embeds the Stable.com widgets as tabs. Each also has its own page: - **Swap** — [https://stable.com/defi/swap](https://stable.com/defi/swap): swap stablecoins within one chain or across chains from a connected non-custodial wallet. Developers can use the same swap through the [Stable Swap API](https://stable.com/docs/stable-swap-api.txt). - **Buy** — [https://stable.com/defi/buy](https://stable.com/defi/buy): buy stablecoins with fiat. - **Sell** — [https://stable.com/defi/sell](https://stable.com/defi/sell): sell stablecoins for fiat. - **Bank** — [https://stable.com/defi/bank](https://stable.com/defi/bank): send and receive bank transfers directly from a non-custodial account. Visitors in the United Kingdom see none of the widgets: the page shows only the account offer, and the `/defi/` pages redirect to the front page. ## Who provides the service Outside the United Kingdom, the page names the Unlimit group entities that provide Stable.com services in the European Economic Area: - **Unlimit EU Ltd** is registered in Cyprus (HE328641), at 125 Georgiou Griva Digeni, Limassol 3101, Cyprus. It is licensed and regulated by the Central Bank of Cyprus as an Electronic Money Institution (authorisation 115.1.3.7). - **Unlimit Crypto Limited** is registered in Cyprus (ΗΕ437355) at the same address. It is authorised by the Cyprus Securities and Exchange Commission as a Crypto-Asset Service Provider (CASP) under Regulation (EU) 2023/1114 on Markets in Crypto-Assets. Which of them provides a given service, and who provides services outside the European Economic Area, is set out in the [FAQ](https://stable.com/faq.md). In the United Kingdom, Stable.com is a trading name of **Unlimit UK Ltd**, registered in England and Wales at 2 Seething Lane, 7th Floor, London, EC3N 4AT (No. 14173267). Unlimit UK Ltd is authorised and regulated by the Financial Conduct Authority under the Electronic Money Regulations 2011 (FRN: 978706) for the issuing of electronic money and provision of payment services. It is a non-bank payment provider ([FCA: using payment service providers](https://www.fca.org.uk/consumers/using-payment-service-providers)) and a member of the Visa, Mastercard, UnionPay, JCB and American Express card associations. Its terms and customer information are at [accounts.unlimit.com](https://www.accounts.unlimit.com/en-gb/legal-documents/). ## More - [Customer terms and information](https://stable.com/legal-documents.md) - [Privacy Centre](https://stable.com/privacy-centre.md) - [Exchange rates](https://www.unlimit.com/exchange-rates/) - Help: [accounts.support@stable.com](mailto:accounts.support@stable.com) --- Source: https://stable.com/faq.md # Frequently Asked Questions > Page: https://stable.com/faq. Stable.com does not show this page to visitors in the United Kingdom; for them the provider is Unlimit UK Ltd — see https://stable.com/index.md. ## What is Stable.com? Stable.com is a brand name for a collection of services offered by providers within the Unlimit Group of companies and made available to customers through the website, app, or other user interface. Services offered under the Stable.com brand are provided by different Unlimit entities (together, “Stable.com providers”, “we”, “us”, or “our” for the purposes of this page). The entity providing services to you depends on where you are located. ## Which Stable.com providers provide services to you? ### Inside the European Economic Area (EEA) If you are an account holder in the European Economic Area, and you use our account services, those services are provided by Unlimit EU Ltd, registered in Cyprus (HE328641), with its registered address at 125 Georgiou Griva Digeni, Limassol 3101, Cyprus. Unlimit EU Ltd is licenced and regulated by the Central Bank of Cyprus as an Electronic Money Institution (authorisation 115.1.3.7). More details are available in the register maintained by the [Central Bank of Cyprus](https://www.centralbank.cy) which also includes the Central Bank's contact details and address. You can also visit the European Banking Authority (EBA) [register](https://euclid.eba.europa.eu/register/pir/disclaimer?returnUrl=%2Fpir%2Fsearch). If you use our on-ramp and off-ramp and swap services, those services are provided and operated by Unlimit Crypto Limited, registered in Cyprus (ΗΕ437355) with its registered address at 125 Georgiou Griva Digeni, Limassol 3101, Cyprus. Unlimit Crypto Limited is authorised by the Cyprus Securities and Exchange Commission (CYSEC) as a Crypto-Asset Service Provider under Regulation (EU) 2023/1114 on Markets in Crypto-Assets, whose authorisation is indicated by European Securities and Marketing Authority (ESMA) [register](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica#InterimMiCARegister). ### Outside the European Economic Area Certain Stable.com branded services may be provided by other Stable.com providers, including (i) Stable.com Ltd, a company incorporated in the British Virgin Islands, which provides such services in accordance with the laws of the British Virgin Islands, as described in the [user terms](https://stable.com/legal/STBL_Stable_User_Terms_Swap_Product_v2_24.06.2026.pdf). --- Source: https://stable.com/legal-documents.md # Customer terms and information > Page: https://stable.com/legal-documents. Stable.com shows one of the two lists below, chosen by the visitor's location: the Unlimit UK Ltd list in the United Kingdom, the Unlimit EU Limited list everywhere else. ## Terms and Conditions and Customer Information for Unlimit EU Limited — outside the United Kingdom ### Accounts and Payment Services #### General - [General Terms and Conditions](https://stable.com/legal/STBL_EU_GTC_v1_19.06.2026.pdf) — In force from 1 July 2025, 0.6 MB #### Card - [Card Terms and Conditions](https://stable.com/legal/STBL_EU_Card_TC__v1_19.06.2026.pdf) — In force from 1 July 2025, 0.4 MB - [Google Pay Terms and Conditions](https://stable.com/legal/STBL_EU_TC_Googlepay_v.1_19.06.2026.pdf) — In force from 13 May 2024, 0.16 MB - [ApplePay Terms and Conditions](https://stable.com/legal/STBL.EU_TC_Applepay_v.01_19.06.2026.pdf) — In force from 13 May 2024, 0.15 MB - [Digital Wallets Terms and Conditions (Mastercard Cards)](https://stable.com/legal/STBL_EU_TC_DIGITALWALLETS_MC_v.01_09.06.2026.pdf) — In force from 13 May 2024, 0.17 MB ### Fees #### In relation to Unlimit EU - [General KYB Fees and Charges for Corporate Customers](https://stable.com/legal/UNL.EU_Unlimit_FeesCharges_Corporate_GENERAL_KYB_12.11.2026.pdf) — In force from 12 November 2026, 0.26 MB - [Standard Fees and Charges for Individual Customers](https://stable.com/legal/STBL_EU_FeesCharges_Individuals_Standard_10.04.2025.pdf) — In force from 10 April 2025, 0.19 MB - [Standard Fees and Charges for Freelance Customers](https://stable.com/legal/STBL_EU_FeesCharges_Freelance_Customers_Standard_10.04.2025.pdf) — In force from 10 April 2025, 0.2 MB - [Card (Corporate Customers EUR) Fees and Charges](https://stable.com/legal/STBL_EU_Corp.Card_Fees_General_EUR_01.07.2024.pdf) — In force from 1 July 2024, 0.36 MB - [Card (Corporate Customers USD) Fees and Charges](https://stable.com/legal/STBL_EU_Corp.Card_Fees_General_USD_01.07.2024.pdf) — In force from 1 July 2024, 0.3 MB #### In relation to Holyheld - [Current Account (Individual) - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_Holyheld_IBAN_20.10.2024.pdf) — In force from 20 October 2024, 0.14 MB - [Physical Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_Mastercard_EU_FeesCharges_Holyheld_Physical_card_20.10.2024.pdf) — In force from 20 October 2024, 0.17 MB - [Virtual Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_Mastercard_EU_FeesCharges_Holyheld_Virtual_card_20.10.2024.pdf) — In force from 20 October 2024, 0.18 MB #### In relation to Simple - [Current Account (Individual) - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_Simple_Europe_UAB_IBAN_10.02.2025.pdf) — In force from 10 February 2025, 0.13 MB - [Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_Mastercard_EUR_FeesCharges_Individuals_SIMPLE_31.01.2024.pdf) — In force from 31 January 2024, 0.16 MB #### In relation to Unicambio - [Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_VisaCard_EUR_FeesCharges_Individuals_UNICAMBIO_22.04.2024.pdf) — In force from 22 April 2024, 0.14 MB #### In relation to EMAS Technology - [Current Account (Individual) - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_EMAS_Technology_GmbH_IBAN_27.01.2025.pdf) — In force from 27 January 2025, 0.13 MB - [Physical Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_EMAS-Technology-GmbH_Individuals_Physical-card_18.11.2024.pdf) — In force from 18 November 2024, 0.18 MB - [Virtual Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_EMAS-Technology-GmbH-_Individuals_Virtual-card_18.11.2024.pdf) — In force from 18 November 2024, 0.18 MB #### In relation to Pure Pay GmbH - [Current Account (Individual) - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_Pure_Pay_GmbH_IBAN_05.03.2025.pdf) — In force from 5 March 2025, 0.13 MB #### In relation to WICKIE STANDARD CONSUMER DEBIT - [Current Account (Individual) - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_GreatIdea_UAB_IBAN_09.12.2025.pdf) — In force from 9 December 2025, 0.12 MB - [Virtual Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_Visa_EU_FeesCharges_GreatIdea_UAB_Virtual_card_09.12.2025.pdf) — In force from 9 December 2025, 0.18 MB #### In relation to KLARA EUROPE - [Current Account (Individual) - Fees and Charges](https://stable.com/legal/UNL.EU_FeesCharges_KLARA_AI_EUROPE_SOCIEDAD_DE_IBAN_20.04.2026.pdf) — In force from 20 April 2026, 0.17 MB - [Virtual Card (Individual) EUR - Fees and Charges](https://stable.com/legal/UNL.EU_Mastercard_EU_FeesCharges_KLARA_AI_EUROPE_SOCIEDAD_DE_Virtual_card_20.04.2026.pdf) — In force from 20 April 2026, 0.24 MB ### General Customer Information - [Security Tips](https://stable.com/legal/STBL_UNLEU_Security_Tips_09042025.pdf) - [Exchange rates](https://www.unlimit.com/exchange-rates/) ### User Terms and Conditions for Crypto products and services #### Inside EEA: (Stable.com by Unlimit Crypto Ltd Services) - [Stable.com User Terms](https://stable.com/legal/2026-10_Stable_User_Terms.pdf) — In force from 7 October 2026 #### Outside the EEA: (Stable.com Ltd (BVI) - Swap Service) - [Stable.com User Terms](https://stable.com/legal/STBL_Stable_User_Terms_Swap_Product_v2_24.06.2026.pdf) — In force from 1 November 2025 ## Terms and Conditions and Customer Information for Unlimit UK Ltd — in the United Kingdom ### General Terms and Conditions for eMoney Accounts - [General Terms and Conditions](https://stable.com/legal/STBL_UNL.UK_GTC_Emoney_Accounts_03.2025.pdf) — In force from 12 March 2025, 0.7 MB ### Card - [Card Services Terms and Conditions](https://stable.com/legal/STBL_UNL.UK_Card_Services_03.2025.pdf) — In force from 12 March 2025, 0.4 MB ### Fees (In relation to Unlimit UK) - [General Fees and Charges for Corporate customers](https://stable.com/legal/UNL.UK_FeesCharges_Corporate_GENERAL_17.03.2025.pdf) — In force from 17 March 2025, 0.3 MB - [General Card Fees and Charges for Corporate customers](https://stable.com/legal/UNL.UK_Corp.Card_FeesCharges_General_17.03.2025.pdf) — In force from 17 March 2025, 0.16 MB - [Standard Fees and Charges for Individual customers](https://stable.com/legal/UNL.UK_FeesCharges_Individuals_Standard_17.03.2025.pdf) — In force from 17 March 2025, 0.37 MB - [Standard Fees and Charges for Freelance customers](https://stable.com/legal/UNL.UK_FeesCharges_Freelance_Customers_Standard_17.03.2025.pdf) — In force from 17 March 2025, 0.36 MB ### General customer information - [Complaint Handling Policy](https://stable.com/legal/UNL.UK-Complaints-Handling-Policy-v1.2-PUBLIC_stable.com.pdf) - [Complaint Form](https://stable.com/legal/UNL.UK_Complaint_Form_v1.2_stable.pdf) - [Security Tips](https://stable.com/legal/UNL.UK_Security_Tips_11.10.2023_Stable.com.pdf) --- Source: https://stable.com/privacy-centre.md # Stable.com’s Privacy Centre > Page: https://stable.com/privacy-centre Welcome to Stable.com’s Privacy Centre. This Centre gives you quick access to: 1. About Stable.com 2. Personal Data Strategic Commitments 3. Stable.com’s Website Privacy Notice 4. Stable.com’s Provider’s Privacy Notices 5. Our [Cookie Notice](https://stable.com/legal/Stable.com_Cookie_Notice_v2.0_19.06.2026.pdf) 6. Responsible AI Notice 7. How to contact us ## About Stable.com Stable.com is a brand name for a collection of services offered by providers in the Unlimit Group of companies whose services are offered to customers through the Website, App, or User Interface. The services, therefore, under the Stable.com brand, are provided by different entities (collectively known as “Stable.com providers” or “we” or “our” in this Privacy Centre). ## Personal Data Commitments **Transparent and accurate:** We want you to understand what personal data we gather about you, why we gather it, and that we care about keeping it accurate and up to date. **Trained and Assessable:** Our Personal Data Strategy and Vision are based on a global data protection program built on a controls framework to support testing and audits. Our staff is trained in privacy and security. **Safe, secure and confidential:** We know you require secure, borderless, quick, and trusted experiences. We take pride in our services, and we must ensure your personal data is kept safe, secure, and confidential. We take all reasonable measures to ensure that your personal data is appropriately protected, including when we need to work with third parties. **Privacy by design and default:** We collect only personal data that we need from you to provide our products and services. We embrace privacy by design and by default into the personal data lifecycle. **Ethical use, retention and deletion:** We keep your personal data only for as long as we need it and strive to delete it afterward, per local law. We do not sell your personal data. [Website Privacy Notice](https://stable.com/legal/STBL_Website_Privacy_Notice_v3.0_23.06.26.pdf): Applies when you visit our Website, App or contact us via the channels available on the Website. How to navigate our Privacy Notices: the products and services are provided by one or more entities in the Unlimit Group of Companies and different Privacy Notices may apply depending on which products and services are made available to you. Through this Privacy Centre, you can access the Privacy Notice based on the product or service you are using. For example, if you are using Unlimit EU Account or Payment Processing services, see the [Unlimit privacy policy](https://www.unlimit.com/privacy-policy/); if made available to you in your region, see the [User Privacy Statement](https://stable.com/legal/STBL_Swap_User_Privacy_Statement_v2_24.06.2026.pdf) when you subscribe to and use the token swap services. To access our Privacy Notices for products offered by Unlimit outside of the EU/EEA region, select the relevant country or jurisdiction on the page. [Cookie Notice](https://stable.com/legal/Stable.com_Cookie_Notice_v2.0_19.06.2026.pdf): Our Cookie Notice sets out our practices for cookies, tags and other online data we gather when you visit our Website. We also explain how you can manage your use of cookies using our cookie banner and cookie settings and your preference settings. ## How do you Contact the data protection team? If you have any questions, contact us at [dpo@unlimit.com](mailto:dpo@unlimit.com). We ask that you not send sensitive data or payment details to the data protection function. ## Privacy documents - [Website Privacy Notice](https://stable.com/legal/STBL_Website_Privacy_Notice_v3.0_23.06.26.pdf) - Privacy Notices - [Unlimit EU](https://www.unlimit.com/privacy-policy/) - [Unlimit Crypto](https://www.crypto.unlimit.com/user-privacy-notice/) - [Crypto Privacy Centre](https://www.crypto.unlimit.com/privacy-centre/) - [Cookie Notice](https://stable.com/legal/Stable.com_Cookie_Notice_v2.0_19.06.2026.pdf) - [User Privacy Notice](https://stable.com/legal/STBL_Swap_User_Privacy_Statement_v2_24.06.2026.pdf) - [Responsible AI Notice](https://stable.com/legal/STBL_Responsible_AI_23.06.2026.pdf) --- Source: https://stable.com/token-2049.md # Stable.com at TOKEN2049 Singapore — can your bank do that? > Page: https://stable.com/token-2049. Meet Stable.com, powered by Unlimit, at TOKEN2049 Singapore, 7–8 October 2026: fiat, stablecoins and DeFi in one global account. Singapore · 7–8 October 2026 · Platinum Sponsor **Fiat, stablecoins and DeFi. One global account. No unnecessary complexity.** [Open account](https://onboarding-kyx.stable.com/auth) · [Book a meeting](https://calendly.com/unlimit-apac-accounts-lena/token2049-meeting?month=2026-09) ## Your business speaks many currencies. Your platform should speak them all Stable.com brings traditional and digital finance together, so you can manage how money enters, moves and leaves your business without navigating disconnected platforms. - **Global account** — Manage multi-currency balances and access local payment details through one account. - **Global money movement** — Send and receive funds through local and international payment rails, with payouts supported in more than 150 currencies. - **Cards and treasury** — Use cards, control business spending, and manage global treasury operations from a unified platform. - **Digital assets and DeFi** — Buy, sell and swap supported digital assets, access tokenised assets and connect to non-custodial DeFi across multiple blockchain networks. > With our newly granted MiCA license, Unlimit is taking over TOKEN2049 Singapore to show Web3 enterprises how we've streamlined compliant, single-passport crypto-fiat infrastructure worldwide. — Michele Fung ## Your money. Onchain. Offchain. Unchained - **Cash in** — Receive funds through local payment details and move traditional currency into supported digital assets. - **Move** — Hold, convert and transfer value across currencies and blockchain networks. Supported swaps come with no slippage and no hidden markups. - **Cash out** — Convert digital assets into traditional currency and send funds through Unlimit's global payment network. No unnecessary detours. No fragmented financial stack. Just a more direct way to move value. ## Freedom to move. Infrastructure to move responsibly Web3 businesses can move faster without treating compliance, payments and treasury as separate problems. One platform. Global infrastructure. Built for what money is becoming. Stable.com is powered by Unlimit's proprietary payment network, spanning more than 180 countries and supporting payouts in more than 150 currencies. **Disclosure.** The platform connects global payment infrastructure with digital asset capabilities through the relevant Unlimit entities and regulatory frameworks. Coverage figures on this page describe Unlimit's proprietary payment network. ## Stable.com in the news - **Finance Magnates, 17 Sep 2026** — [Unlimit rebrands business accounts as Stable.com, begins client migration](https://www.tradingview.com/news/financemagnates:285fb397e094b:0-unlimit-rebrands-business-accounts-as-stable-com-begins-client-migration/). Unlimit has rebranded its business accounts operation as Stable.com, moving European clients to a new platform that will combine its existing account and payment products with planned digital asset and decentralised finance services. - **Electronic Payments International, 18 Sep 2026** — [Unlimit adds Stable.com to Polygon to enable direct bank transfers](https://www.electronicpaymentsinternational.com/news/unlimit-adds-stable-com-to-polygon/). Unlimit has announced the expansion of Stable.com into the Polygon Open Money Stack. The integration enables businesses and individual users to initiate bank transfers directly from self-custody wallets on the Polygon network using USDT and PayPal USD (PYUSD). Meet the Stable.com team at TOKEN2049 Singapore and discover a simpler way to manage traditional money, stablecoins and on-chain finance through one global platform. --- Source: https://stable.com/coverage.md # Networks, assets, currencies and countries > What the Stable.com swap, buy and sell widgets support. This is a snapshot: the config APIs linked in each section are the live source and can change before this file does. Visitors in the United Kingdom get none of the widgets. ## Swap Source: https://api-defi.stable.com/openapi/swap/config/all Stablecoins that can be swapped, by chain. Only the assets listed here are swapped; native coins are not. Developers can use the same swap through the [Stable Swap API](https://stable.com/docs/stable-swap-api.txt). - Ethereum: USDT, USDC, PYUSD, USDP, USDG, RLUSD - Solana: USDT, USDC, PYUSD, USDG, USDP - BNB Smart Chain: USDT, USDC - Tron: USDT - Polygon: USDC, USDT, PYUSD ## Buy stablecoins with fiat Source: https://api-defi.stable.com/config/onramp - Ethereum: USDT, USDC, PYUSD, USD1, FDUSD - Solana: USDT, USDC - BNB Smart Chain: USDT, USDC, FDUSD - Tron: USDT - Polygon: USDT, USDC - Arbitrum One: USDT, USDC - Base: USDC - Celo: USDT, USDC - Optimism: USDC Fiat currencies: AED, AUD, BRL, CAD, CHF, COP, CRC, CZK, DKK, EUR, GBP, HKD, HUF, IDR, ILS, JPY, KES, KGS, KRW, KZT, MXN, MYR, NOK, OMR, PAB, PEN, PHP, PLN, RON, SEK, SGD, THB, TWD, USD, VND, ZAR (36). ## Sell stablecoins for fiat Source: https://api-defi.stable.com/config/offramp - Ethereum: USDT, USDC, USD1 - Solana: USDT, USDC - BNB Smart Chain: USDT, USDC - Tron: USDT - Polygon: USDT, USDC - Arbitrum One: USDT, USDC - Base: USDC - Celo: USDT, USDC - Optimism: USDC Fiat currencies: AED, AUD, BGN, BRL, CAD, CHF, COP, CRC, CZK, DKK, EUR, GBP, HKD, HUF, IDR, ILS, JPY, KES, KGS, KRW, KZT, MXN, MYR, NGN, NOK, OMR, PAB, PEN, PHP, PLN, RON, SEK, SGD, THB, TWD, TZS, USD, VND, ZAR (39) — the buy currencies plus BGN, NGN, TZS. Payment and payout methods depend on the country and currency and are offered in the widget. ## Countries Buying and selling is available in 223 countries and territories. It is not available in: Afghanistan, Bahamas, Belarus, Benin, Burkina Faso, Central African Republic, Cuba, Democratic Republic of the Congo, Haiti, India, Iran, Iraq, Libya, Mali, Myanmar, North Korea, Russia, Somalia, South Sudan, Sudan, Syria, United Kingdom, Venezuela, Western Sahara, Yemen, Zimbabwe. ## Wallets The swap works with your own self-custody wallet: - EVM chains: MetaMask, Coinbase, Phantom, Trust Wallet, Rabby Wallet - Solana: MetaMask, Phantom, Trust Wallet - Tron: TronLink - Any other wallet through WalletConnect --- Source: https://stable.com/docs/stable-swap-api.txt # Stable Swap API — Integration Guide HTTP API for **single-chain swaps** (stablecoin ⇄ stablecoin within one chain) and **cross-chain swaps** (atomic swap between two chains). * **Base URL:** `https://api-defi.stable.com/openapi` * **Route prefix:** `/swap` * **Transport:** JSON over HTTPS, `Content-Type: application/json` No credentials are required. --- ## 0. Generating a client from this document Paste the block below into a coding agent together with the whole of this document. It asks what you need first, then writes the code. ````text You are integrating with the Stable Swap API. The complete reference is the document below this prompt — treat it as the only source of truth. Do not invent endpoints, fields or values that are not in it; if something you need is missing, ask me. STEP 1 — Ask me these questions and wait for my answers before writing any code. Offer the recommended default for each, so I can answer "defaults" and you proceed. 0. Is the document below the current version of the API reference? If I am not certain, ask me to obtain the latest one before we start. A stale field list is the likeliest reason generated code compiles and then fails against the live API, and you have no way to detect it from the text alone. 1. Language and runtime. (default: Python 3.11+, `requests` + `eth-account`) 2. What to build: a) a single-file demo script that runs one swap end to end ← default b) a reusable client library — typed models, no CLI c) a full service — my own HTTP API, persistence, background pollers 3. Which flows to implement: a) single-chain gasless — no on-chain calls from me ← default b) single-chain where I submit the Pool contract call myself c) cross-chain gasless d) cross-chain where I submit the source lock myself 4. Parameters for the first run: chain id, assetFrom, assetTo, amount, addressFrom, addressTo. 5. Key handling: a) private key from an environment variable, signing inside the code ← default b) delegate signing to a callback or an external wallet c) no signing at all — quote and read-only calls only 6. Values the API does not serve, needed for some flows (see §9): - any cross-chain flow (3c or 3d) → the HTLC contract address and the EVM chain id for the source chain; - self-paid single-chain (3b) → the Pool contract address and its ABI; - self-paid cross-chain (3d) → the HTLC contract ABI as well. Do I have them? If not, we can only build the gasless single-chain flow. 7. Base URL, if not the production one in this document. 8. Run mode: one-shot, exiting when the order settles ← default, or a long-running poller handling many orders. 9. Anything to log or persist beyond stdout? (default: structured stdout only) STEP 2 — Then write the code, honouring every rule below. These are the parts of this API that are easy to get wrong. * A field equal to its zero value is ABSENT from a response. Never distinguish `undefined` from `false` / `0` / `""`. In particular `valid` is missing when validation failed, and `status` is missing while a cross-chain swap is in flight. The quote response is the exception: `precision`, `balance`, `min`, `max`, `nativeFee`, `tokenFee` and `nativeFeeUsd` are declared `optional` precisely so a zero survives, which is why the example below carries `"tokenFee":0`. * `secretHash`, `sessionPubkey`, `sessionSignature` and `maintainerSignature` are plain lowercase hex with NO `0x` prefix. Transaction ids use the native chain form, which on EVM does include `0x`. Add and strip prefixes deliberately. * Amounts in requests, and `amountFrom` / `amountTo` / `resultingAmount*` / `executionFee*` in responses, are decimal strings in HUMAN units. Balances and allowances from `account/*` are decimal strings in RAW units — divide by the asset `precision` from `/swap/config/all`. Use exact decimal arithmetic, never float — note that `min`, `max`, `balance` and `tokenFee` arrive as JSON numbers, so convert them through their string form before doing decimal maths with them. * `POST /swap/status` takes exactly one of `amountFrom` or `amountTo`. * `POST /swap/notify/userPermitSignatures` takes exactly one of `orderId` for single-chain or `secretHash` for cross-chain. * Branch on `method` from the create response: `permit` or `permit2` → sign `permit2_typed_data` and send `permitSignature`; `signature` → sign `user_auth_typed_data` and send `userAuthSignature`; `method` absent while `gasLessData` is present → Solana, co-sign and broadcast that transaction instead. * `permit2_typed_data` and `user_auth_typed_data` are snake_case keys holding a complete EIP-712 document with `types`, `primaryType`, `domain` and `message`. Use `types`, `primaryType` and `message` verbatim. The `domain` always carries all five keys (`name`, `version`, `chainId`, `verifyingContract`, `salt`) even when empty, which a strict library rejects as a mismatch against `types.EIP712Domain` — filter `domain` down to exactly the keys `types.EIP712Domain` declares, and never add one it does not. Drop such a key only when it is empty; a non-empty undeclared key is a broken document, so fail rather than sign. Whether `types` should keep its own `EIP712Domain` entry depends on your library — some require it, some reject it. `chainId` arrives as a hex string such as `"0x89"`. See §6. * `permitSignature` and `userAuthSignature` accept bare hex or a `0x` prefix — either works. Every other hex field must be bare. For `method: "signature"` leave `permitSignature` empty and send only `userAuthSignature`. * Quote the amount you actually intend to swap. `POST /swap/status` does not enforce the pair's limits — it returns `min` and `max` and prices anything, so compare against them yourself. `create/*` rejects an out-of-range amount with the bound in `details.value`. * Respect `deadline` from the create response. Check it before every subsequent step and abandon the order once it has passed — there is no `expired` status, the order simply stays `initialized`. * For a gasless order, call `create/*` within 60 seconds of `POST /swap/status`, passing the identical parameter set and the identical amount STRING, or the fee is recalculated. * HTTP 200 with `status: "error"` is a failure. Read the body, not the status code. Poll with a bounded interval and an overall timeout. * Cross-chain: the two `POST /swap/validate` types are independent. Call `lockSourceGasless` as soon as `sourceLockTransactionId` appears and `lockDestination` as soon as `destinationLockTransactionId` appears, inside the same polling loop — do not serialise them. A `409` from `validate` means the lock is not on-chain yet; keep polling and call again. * `POST /swap/notify/userSessionSignature` needs both validations to have passed, and a 65-byte signature whose `v` is 27 or 28. * `account/allowances` results come back in arbitrary order — match them on `(chainId, address, token)`. * On an error, `message` is a generic status text; the useful part is `details`, a `field → reason` map. Surface both. * Do not blind-retry a `500`. An unknown order id returns `500` from every endpoint except `notify/userLockSourceTransaction`, which returns `404`; a missing required query parameter returns `500` with an empty `message`. Retry a `500` only for a request you know is well formed and refers to an order we returned. Use the call sequences in §16 as the control flow. ```` --- ## 1. Endpoints | Method | Path | Purpose | |---|---|---| | `GET` | `/swap/config/all` | Supported chains and assets | | `POST` | `/swap/status` | Quote amounts, fees, limits, available liquidity | | `POST` | `/swap/create/singleChain` | Open a single-chain order | | `POST` | `/swap/create/crossChain` | Open a cross-chain order | | `POST` | `/swap/notify/userPermitSignatures` | Submit signatures (gasless) | | `POST` | `/swap/notify/singleChainStatus` | Report your single-chain transaction | | `POST` | `/swap/notify/userLockSourceTransaction` | Report your cross-chain source lock | | `POST` | `/swap/notify/userSessionSignature` | Submit the session claim signature | | `POST` | `/swap/notify/userSignedTransaction` | Return the signed Solana transaction for us to broadcast | | `POST` | `/swap/validate` | Verify our lock against on-chain state | | `GET` | `/swap/singleChain/status` | Poll a single-chain order | | `GET` | `/swap/crossChain/status` | Poll a cross-chain order | | `POST` | `/swap/account/info` | Native and token balances across chains | | `POST` | `/swap/account/allowances` | Pool and Permit2 allowances | --- ## 2. `GET /swap/config/all` No parameters. **Response** | Field | Type | Description | |---|---|---| | `chainDict` | map | Supported chains, keyed by chain id. | | `chainDict[].name` | string | Chain name. | | `chainDict[].code` | string | Chain ticker. | | `assetDict` | map | Assets per chain, same keys as `chainDict`. | | `assetDict[].assets[].asset` | string | Asset symbol, used as `assetFrom` / `assetTo`. | | `assetDict[].assets[].precision` | int | Token decimals — converts between the human-unit amounts this API takes and raw on-chain units. Read it per asset per chain: the same symbol differs between chains, e.g. USDT is 6 on Ethereum and 18 on BNB Smart Chain. | | `assetDict[].assets[].address` | string | Token contract address. | | `assetDict[].assets[].programAddress` | string | Solana only — SPL token-program address. | ### Chain ids | Chain id | Chain | |---|---| | `101` | Ethereum | | `102` | Solana | | `103` | BNB Smart Chain | | `104` | Tron | | `106` | Polygon | **Example** ```json // GET /swap/config/all { "chainDict": { "101": { "name": "Ethereum", "code": "ETH" }, "103": { "name": "BSC", "code": "BSC" } }, "assetDict": { "101": { "assets": [ { "asset": "USDT", "precision": 6, "address": "0xdAC17F95…" }, { "asset": "USDC", "precision": 6, "address": "0xA0b86991…" } ]}, "103": { "assets": [ { "asset": "USDT", "precision": 18, "address": "0x55d39832…" } ]} } } ``` --- ## 3. `POST /swap/status` — quote Call before `create/*`. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `chainFrom` | string | ✔ | Source chain id. | | `chainTo` | string | ✔ | Destination chain id. For a single-chain quote pass the same value as `chainFrom`; a different value makes it a cross-chain quote. | | `assetFrom` | string | ✔ | Source asset symbol. | | `assetTo` | string | ✔ | Destination asset symbol. | | `amountFrom` | string — decimal, human units | ◑ | Amount to send. Send exactly one of `amountFrom` / `amountTo`. | | `amountTo` | string — decimal, human units | ◑ | Amount to receive; the source amount is solved backwards. | | `addressFrom` | string | – | Sender. Leave empty for an estimate without a connected wallet; with an address the quote is exact for that account. | | `addressTo` | string | – | Recipient. | | `gasLess` | bool | – | `true` quotes the gasless route, where the fee is taken in the source token instead of native gas. | **Response** — the body is `{ "asset": { … } }`; the fields below are inside that object. | Field | Type | Description | |---|---|---| | `asset` | string | Source asset symbol. | | `precision` | int | Source token decimals. | | `balance` | float | Maximum amount this swap can currently output, in destination-asset units. | | `min` | float | Minimum `amountFrom` for this asset. | | `max` | float | Maximum `amountFrom` for this asset. | | `amountFrom` | string — decimal, human units | Resolved source amount. Echoes your `amountFrom` when you sent one; when you sent `amountTo` instead, it is the source amount solved backwards, grossed up to cover the fee. | | `amountTo` | string — decimal, human units | Resolved destination amount, after the protocol fee. | | `tokenFee` | float | Protocol fee, charged in the source token. | | `executionFeeNative` | string — decimal, human units | Native amount to attach to your on-chain call. May be `"0"` — always in gasless mode, and on chains where no extra native fee applies. | | `executionFeeUSD` | string | The same fee in USD. | | `address` | string | Source token contract address. | | `programAddress` | string | Solana token-program address. | **Example** ```json // POST /swap/status {"chainFrom":"103","assetFrom":"USDC","chainTo":"103","assetTo":"USDT", "amountFrom":"10","addressFrom":"0xb1Ce…e3cD","addressTo":"0xb1Ce…e3cD","gasLess":false} // response {"asset":{ "asset":"USDC","precision":18,"balance":155599.55,"min":10,"max":1000000, "tokenFee":0,"address":"0x24A11478F452Fb9474E0f8930eB58942F3f6Ef90", "amountFrom":"10","amountTo":"10", "executionFeeNative":"0","executionFeeUSD":"0" }} ``` --- ## 4. `POST /swap/create/singleChain` Opens a single-chain order and returns a signature authorising the Pool contract to execute it. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `chainFrom` | string | ✔ | Chain id. Both assets must exist on it. | | `assetFrom` | string | ✔ | Source asset symbol. | | `assetTo` | string | ✔ | Destination asset symbol. May equal `assetFrom`. | | `amountFrom` | string — decimal, human units | ✔ | Amount to send. | | `addressFrom` | string | ✔ | Payer and token owner. | | `addressTo` | string | ✔ | Recipient. May equal `addressFrom`. | | `gasLess` | bool | – | `true` → we submit the transaction and take the fee in the source token. | | `device` | string | – | Stable identifier of the end user's client. | **Response** | Field | Type | Description | |---|---|---| | `orderId` | string — UUID | Order identifier, used for `notify/*` and `singleChain/status`. | | `maintainerSignature` | string — hex, no `0x`, 65 bytes | Our authorisation over the order parameters; pass it to the Pool contract call. Last byte is `1b`/`1c` on EVM and Tron, `00`/`01` on Solana. | | `nonce` | string — decimal | The per-address nonce the signature covers. | | `deadline` | int64 — Unix seconds | The signature is valid until this time. The window is short — minutes, not hours — so collect the user's signature promptly. | | `executionFeeNative` | string — decimal, human units | Native amount to attach to the on-chain call. `"0"` for gasless. | | `executionFeeUSD` | string | The same fee in USD. | | `method` | string | Gasless route for this order: `permit` / `permit2` on EVM, `signature` on Tron. Absent for Solana and for non-gasless orders. | | `permit2_typed_data` | object | EIP-712 typed data for the user to sign, authorising the token pull. Present for `permit` and `permit2`. | | `user_auth_typed_data` | object | Second EIP-712 document for the user to sign. Present for `signature`. | | `gasLessData` | string — base64 | Solana only — a complete transaction, already signed by us and with our account as fee payer. Add the user's signature and broadcast it. | **Example** ```json // POST /swap/create/singleChain — you pay gas {"chainFrom":"103","assetFrom":"USDC","assetTo":"USDT","amountFrom":"100", "addressFrom":"0xb1Ce…e3cD","addressTo":"0xb1Ce…e3cD","gasLess":false} // response {"data":{ "orderId":"c06fba34-7ac6-4376-8e6a-9bf593708eff", "nonce":"55","deadline":1788936742, "maintainerSignature":"2ada42b2…16751b", "executionFeeNative":"0","executionFeeUSD":"0" }} ``` **Example** ```json // POST /swap/create/singleChain — gasless, and what the typed data looks like {"chainFrom":"106","assetFrom":"USDC","assetTo":"USDT","amountFrom":"1000", "addressFrom":"0x3b81…1E87","addressTo":"0x3b81…1E87","gasLess":true} // response {"data":{ "orderId":"119b3298-c9e9-4f62-b846-14f3ad1bb65c", "nonce":"1","deadline":1788934145, "maintainerSignature":"f280b390…e2fb1b", "executionFeeNative":"0","executionFeeUSD":"0.0121", "method":"permit", "permit2_typed_data":{ "domain":{ "name":"USD Coin","version":"2","chainId":"0x89", "verifyingContract":"0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359", "salt":"" }, "types":{ "EIP712Domain":[ {"name":"name","type":"string"},{"name":"version","type":"string"}, {"name":"chainId","type":"uint256"},{"name":"verifyingContract","type":"address"} ], "Permit":[ {"name":"owner","type":"address"},{"name":"spender","type":"address"}, {"name":"value","type":"uint256"},{"name":"nonce","type":"uint256"}, {"name":"deadline","type":"uint256"} ] }, "primaryType":"Permit", "message":{ "owner":"0x3b81Dcef90299069D953Cf2a075D84CcDf261E87", "spender":"0xCfC1bc6013eD89D484c626dd9ee5EB7bc1a1d9Da", "value":"1000000000","nonce":"0","deadline":"1788934145" } } }} ``` **Example** — Solana, gasless ```json // POST /swap/create/singleChain {"chainFrom":"102","assetFrom":"USDT","assetTo":"USDC","amountFrom":"100", "addressFrom":"BEy9gmf9…cJ47","addressTo":"BEy9gmf9…cJ47","gasLess":true} // response — gasLessData instead of typed data, and no `method` {"data":{ "orderId":"132a3eaa-875f-452e-b808-aa6c13b41d83", "nonce":"10","deadline":1788940633, "maintainerSignature":"91f44970…b46b3d00", "gasLessData":"AvgLzJ7NU3dohJ+Pyk1BcFC6B/fbrzwYh6P/Uxm6eIOO…AAAA", "executionFeeNative":"0","executionFeeUSD":"0.0015" }} ``` **Example** — Solana, you pay gas ```json // POST /swap/create/singleChain {"chainFrom":"102","assetFrom":"USDC","assetTo":"USDT","amountFrom":"100", "addressFrom":"BEy9gmf9…cJ47","addressTo":"BEy9gmf9…cJ47","gasLess":false} // response — no gasLessData and no method; you assemble the call yourself {"data":{ "orderId":"1fc63457-9c8b-438c-a257-ceb17271d508", "nonce":"11","deadline":1788940864, "maintainerSignature":"b30ab97d…3a378301", "executionFeeNative":"0","executionFeeUSD":"0" }} ``` --- ## 5. `POST /swap/create/crossChain` Opens a cross-chain order. We generate a secret and return only its hash; that hash identifies the order for the rest of the flow. **Request** — as single-chain, plus: | Field | Type | Req. | Description | |---|---|---|---| | `chainTo` | string | ✔ | Destination chain id. Must differ from `chainFrom`. | | `sessionPubkey` | string — hex, no `0x` | ✔ | Public key of an ephemeral session key you generate per order: a 65-byte uncompressed secp256k1 key (`04` + X + Y). It authorises the final claim; keep the private half client-side. | **Response** | Field | Type | Description | |---|---|---| | `secretHash` | string — hex, no `0x`, 64 chars | Identifier of the cross-chain order, used in every subsequent call. | | `orderId` | string — UUID | Also returned, but the cross-chain endpoints do not accept it. Use `secretHash`. | | `maintainerSignature` | string — hex, no `0x` | Our authorisation over the order parameters; pass it to the HTLC contract call. | | `nonce` | string — decimal | The per-address nonce the signature covers. | | `deadline` | int64 — Unix seconds | The signature is valid until this time. | | `resultingAmountFrom` | string — decimal, human units | Amount that will be locked on the source chain. In gasless mode the token fee is already deducted. | | `resultingAmountTo` | string — decimal, human units | Amount released on the destination chain, after the protocol fee. | | `executionFeeNative` | string — decimal, human units | Native amount to attach to the on-chain call. `"0"` for gasless. | | `executionFeeUSD` | string | The same fee in USD. | | `method` | string | Gasless route for this order: `permit` / `permit2` on EVM, `signature` on Tron. Absent for Solana and for non-gasless orders. | | `permit2_typed_data` | object | EIP-712 typed data for the user to sign. Present for `permit` and `permit2`. | | `user_auth_typed_data` | object | Second EIP-712 document for the user to sign. Present for `signature`. | | `gasLessData` | string — base64 | Solana only — a complete transaction, already signed by us and with our account as fee payer. Add the user's signature and broadcast it. | **Example** ```json // POST /swap/create/crossChain — you pay gas {"chainFrom":"103","chainTo":"101","assetFrom":"USDC","assetTo":"USDT","amountFrom":"100", "addressFrom":"0xb1Ce…e3cD","addressTo":"0xb1Ce…e3cD","gasLess":false, "sessionPubkey":"04c389b25f13dde16130f8afe01d63a4a237f74659e7ada037f3da0a76c8f83b0c7053ac3502bd747f44b0f0d81aaa4e56704f3cb1b25ccfa20f018e52b234275f"} // response {"data":{ "secretHash":"73d71e858394452de673dc0e5a31369f80a9910dd7ec1ee96d5706d5d07fdc7d", "orderId":"036563ca-4c61-468c-b925-abb62fcaa104", "nonce":"54","deadline":1788935651, "maintainerSignature":"84f99021…964e0c1b", "resultingAmountFrom":"100","resultingAmountTo":"100", "executionFeeNative":"0.002335068004210441","executionFeeUSD":"1.76" }} ``` --- ## 6. `POST /swap/notify/userPermitSignatures` Starts execution of a **gasless** order on EVM and Tron. After this call we submit the transaction; you poll for the result. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `orderId` | string — UUID | ◑ | Identifies a single-chain order. | | `secretHash` | string — hex, no `0x` | ◑ | Identifies a cross-chain order. Send exactly one of `orderId` / `secretHash`. | | `permitSignature` | string — hex | ◑ | Signature over `permit2_typed_data`. Send for `permit` and `permit2`. | | `userAuthSignature` | string — hex | ◑ | Signature over `user_auth_typed_data`. Send for `signature`. | ### Signing the typed data | Rule | Detail | |---|---| | Filter the domain | `domain` always carries `name`, `version`, `chainId`, `verifyingContract`, `salt`, even when empty. Sign only the keys `types.EIP712Domain` declares. A strict library rejects the document otherwise. | | Non-empty undeclared key | Do not drop it — the document is inconsistent, so fail. | | Never add a key | The declared list is what the hash is computed over. | | `types.EIP712Domain` entry | Some libraries require it, some reject it. Keep or drop to suit yours. | | `chainId` | Hex string, e.g. `"0x89"`, not a number. | | `types`, `primaryType`, `message` | Use as returned. | | `message.spender` | The Pool contract — the same one `allowancePool` reports. | | Nonces | `data.nonce` (order) and `message.nonce` (token permit) are unrelated. | | Signature encoding | Bare hex or `0x` — both accepted here only. For `signature`, leave `permitSignature` empty. | **Response** | Field | Type | Description | |---|---|---| | `data.orderId` | string | The identifier you sent. | **Example** ```json // POST /swap/notify/userPermitSignatures {"orderId":"6529fb19-81f0-4e3f-9501-a36b28032af4", "permitSignature":"0xaa96a1a0…03f581c"} // response {"data":{"orderId":"6529fb19-81f0-4e3f-9501-a36b28032af4"}} ``` --- ## 7. `POST /swap/notify/singleChainStatus` Use this when you submitted the Pool contract call yourself. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `orderId` | string — UUID | ✔ | The order. | | `status` | string | ✔ | `success` once your transaction is submitted. | | `transactionId` | string — native chain form | ✔ | Your transaction id. | **Response:** - `{ "data": {} }` **Example** ```json // POST /swap/notify/singleChainStatus {"orderId":"c06fba34-7ac6-4376-8e6a-9bf593708eff","status":"success", "transactionId":"0x828c88d4c703d88fa3a836209e50a1bafd6e12f9a2c01f3753760ae738dcfab4"} // response {"data":{}} ``` **Example** — Solana, where `transactionId` is a base58 signature ```json // POST /swap/notify/singleChainStatus {"orderId":"132a3eaa-875f-452e-b808-aa6c13b41d83","status":"success", "transactionId":"5xdsRYtKpGJrQczMZYxA5PHKVrLp7dxj3UVSLph2Fbot5SxKFfcrsfhXRzs7ERnpEroFoW97gvWXzTBPtFATpVse"} // response {"data":{}} ``` --- ## 8. `POST /swap/notify/userLockSourceTransaction` Use this when you locked funds in the source-chain contract yourself. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `secretHash` | string — hex, no `0x`, 32 bytes | ✔ | The order. | | `transactionID` | string — native chain form | ✔ | Your source-chain lock transaction id. | After this call we lock the mirrored amount on the destination chain. The call is idempotent. **Response:** - `{ "data": {} }`. **Example** ```json // POST /swap/notify/userLockSourceTransaction {"secretHash":"73d71e858394452de673dc0e5a31369f80a9910dd7ec1ee96d5706d5d07fdc7d", "transactionID":"0xff998686f34316a4c80cde5f547b78c00e469ebaf918ad3ffd35a0035393a6e5"} // response {"data":{}} ``` --- ## 9. `POST /swap/notify/userSessionSignature` The final client action of a cross-chain swap: the session key signs the secret hash, authorising us to complete the claim on both chains. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `secretHash` | string — hex, no `0x`, 32 bytes | ✔ | The order. | | `sessionSignature` | string — hex, no `0x`, 65 bytes | ✔ | Signature by the private half of `sessionPubkey`, with `v` of `27` or `28`. | **What to sign** — EIP-712, primary type `Claim`: ``` domain { name: "CrossChainHTLC", version: "1", chainId: , verifyingContract: } message { secretHash: bytes32 } ``` `chainId` here is the source chain's **EVM** chain id — `1` for Ethereum, `56` for BNB Smart Chain, `137` for Polygon — not the internal chain id from §2. The two are different numbering schemes, and this API does not report the EVM one anywhere, so ask us for it. Signing with `103` instead of `56` produces a signature the contract rejects. `verifyingContract` depends on the deployment — ask us: | Flow | What to ask for | |---|---| | Single-chain, gasless | nothing | | Single-chain, you pay gas | Pool contract address + ABI | | Cross-chain, gasless | HTLC contract address | | Cross-chain, you pay gas | HTLC contract address + ABI + source EVM chain id | Call `POST /swap/validate` before this endpoint: `lockDestination` always, and `lockSourceGasless` as well for a gasless order. **Response:** - `{ "data": {} }`. **Example** ```json // POST /swap/notify/userSessionSignature {"secretHash":"73d71e858394452de673dc0e5a31369f80a9910dd7ec1ee96d5706d5d07fdc7d", "sessionSignature":"57a9cb31f3615135426cb5062c4abadce467ce7c9426745e583ce2be2b01b32574406debd743755fef9397ef03ffa8bfa20a92005a22e2a460065c8363409b471b"} // response {"data":{}} ``` --- ## 10. `POST /swap/notify/userSignedTransaction` Solana only. Hands us back the transaction we prepared, after the user has signed it. We broadcast it; you do not. This is what `gasLessData` is for: a gasless Solana order returns a complete transaction, already signed by us and with our account as fee payer. Add the user's signature and send the result here. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `orderId` | string — UUID | ◑ | Identifies a single-chain order. Send exactly one of `orderId` / `secretHash`. | | `secretHash` | string — hex, no `0x` | ◑ | Identifies a cross-chain order. | | `signedTransaction` | string — base64 | ✔ | The `gasLessData` transaction with the user's signature added. | **Response** | Field | Type | Description | |---|---|---| | `data.orderId` | string | The identifier you sent: the order id for single-chain, the secret hash for cross-chain. | The embedded blockhash expires about a minute after we build the transaction, far sooner than `deadline`. Send it promptly; once expired, create a new order. **Example** ```json // POST /swap/notify/userSignedTransaction {"orderId":"c06fba34-7ac6-4376-8e6a-9bf593708eff", "signedTransaction":"AvgLzJ7NU3dohJ+Pyk1BcFC6B/fbrzwYh6P/Uxm6eIOO…AAAA"} // response {"data":{"orderId":"c06fba34-7ac6-4376-8e6a-9bf593708eff"}} ``` --- ## 11. `POST /swap/validate` Confirms that a lock we made matches your order. Cross-chain only. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `secretHash` | string — hex, no `0x`, 32 bytes | ✔ | The order. | | `type` | string | ✔ | `lockDestination` — our destination lock, for every cross-chain swap. `lockSourceGasless` — our source lock, gasless only. | **Response** | Field | Type | Description | |---|---|---| | `valid` | bool | `true` when on-chain state matches the order. Absent when false. | | `type` | string | The type you requested. | | `transactionId` | string — native chain form | The lock transaction that was inspected. | | `secretHash` | string — hex | The order. | | `amount` | string — decimal, human units | Amount locked: the destination amount for `lockDestination`, the source amount for `lockSourceGasless`. | | `token` | string | Token contract on the inspected chain. | | `chainId` | int | Chain id of the inspected chain. | | `recipient` | string | `addressTo` for `lockDestination`, `addressFrom` for `lockSourceGasless`. | | `destinationLockTime` | int64 — Unix seconds | When the destination lock expires. `lockDestination` only. | | `sourceLockTime` | int64 — Unix seconds | When the source lock expires. `lockDestination` only. | | `nonce` | string — decimal | The nonce the source lock used. `lockSourceGasless` only. | | `deadline` | string — Unix seconds | Signature deadline of the source lock. `lockSourceGasless` only. | **Example** ```json // POST /swap/validate {"secretHash":"73d71e858394452de673dc0e5a31369f80a9910dd7ec1ee96d5706d5d07fdc7d", "type":"lockDestination"} // response {"data":{ "valid":true,"type":"lockDestination", "transactionId":"0x8d0fe9ba3dc793e07e2ca1650827be30eb0d276fda7d7f3361b557c51a940693", "secretHash":"73d71e85…07fdc7d", "amount":"100","token":"0xc802691590d751ACa78729B2dc03b41f2578e557", "chainId":101,"recipient":"0xb1Ce…e3cD", "destinationLockTime":1788939024,"sourceLockTime":1788937164 }} ``` --- ## 12. `GET /swap/singleChain/status` **Query:** `orderId` — UUID, required. **Response** | Field | Type | Description | |---|---|---| | `status` | string | Always present. `initialized` from creation, then `success` or `error`. | | `swapTransactionId` | string — native chain form | The executing transaction id, once known. | | `message` | string | Detail when `status` is `error`. | **Example** — two polls of one order. ```json // GET /swap/singleChain/status?orderId=c06fba34-7ac6-4376-8e6a-9bf593708eff // while it is still open {"data":{"status":"initialized"}} // once it has executed {"data":{ "status":"success", "swapTransactionId":"0x828c88d4c703d88fa3a836209e50a1bafd6e12f9a2c01f3753760ae738dcfab4" }} ``` --- ## 13. `GET /swap/crossChain/status` **Query:** `secretHash` — hex, no `0x`, required. **Response** | Field | Type | Description | |---|---|---| | `status` | string | Absent while the swap is in flight; then `success`, `error` or `refunded`. | | `message` | string | Detail for a failure or refund. | | `sourceLockTransactionId` | string — native chain form | Lock on the source chain — yours, or ours in gasless mode. | | `destinationLockTransactionId` | string — native chain form | Our lock on the destination chain. | | `destinationClaimTransactionId` | string — native chain form | Destination claim; the recipient has the funds. | | `sourceClaimTransactionId` | string — native chain form | Source claim. | | `sourceRefundTransactionId` | string — native chain form | Source refund. | | `destinationRefundTransactionId` | string — native chain form | Destination refund. | There is no `status` to poll until the swap is over. `status` arrives **after** the claim transaction ids. **Example** — three successive polls of one order. ```json // 1. after the source lock was reported {"data":{"sourceLockTransactionId":"0xff998686…93a6e5"}} // 2. after we locked the destination — this is the signal to call POST /swap/validate {"data":{ "sourceLockTransactionId":"0xff998686…93a6e5", "destinationLockTransactionId":"0x8d0fe9ba…940693" }} // 3. after both claims were broadcast; `status` still to come {"data":{ "sourceLockTransactionId":"0xff998686…93a6e5", "destinationLockTransactionId":"0x8d0fe9ba…940693", "sourceClaimTransactionId":"0x938e89c0…661421", "destinationClaimTransactionId":"0x8a0fedaa…0de68b" }} ``` --- ## 14. `POST /swap/account/info` Balances across several chains in one round trip. **Request** | Field | Type | Req. | Description | |---|---|---|---| | `accounts` | map | ✔ | 1–10 entries, one address per chain. | **Response** | Field | Type | Description | |---|---|---| | `chains[].error` | string | Set when the lookup for that chain failed; the other fields are then meaningless. | | `chains[].nativeBalance` | string — decimal, raw units | Native balance. | | `chains[].tokens[].asset` | string | Asset symbol. | | `chains[].tokens[].address` | string | Token contract address. | | `chains[].tokens[].balance` | string — decimal, raw units | Token balance; divide by the asset's `precision`. | | `chains[].accountType` | string | EVM only: `EOA` or `EIP7702`. | **Example** ```json // POST /swap/account/info {"accounts":{"103":"0xb1Ce525A223DB37BbbC5636D1dd70f7bfeF6e3cD"}} // response {"chains":{"103":{ "nativeBalance":"15081044701179892657", "tokens":[ {"asset":"USDT","address":"0xc802691590d751ACa78729B2dc03b41f2578e557", "balance":"21883819820322973819523755"}, {"asset":"USDC","address":"0x24A11478F452Fb9474E0f8930eB58942F3f6Ef90", "balance":"999999991852019979013241193528305"} ], "accountType":"EOA" }}} ``` --- ## 15. `POST /swap/account/allowances` **Request** | Field | Type | Req. | Description | |---|---|---|---| | `queries` | array | ✔ | 1–50 entries. | | `queries[].chainId` | int | ✔ | Chain id as a number. | | `queries[].address` | string | ✔ | Owner address. | | `queries[].token` | string | – | Token contract address or asset symbol. Omit for every configured token on that chain and address. | **Response** | Field | Type | Description | |---|---|---| | `results[].chainId` | int | Chain id. | | `results[].address` | string | Owner address. | | `results[].token` | string | Resolved token address. | | `results[].allowancePool` | string — decimal, raw units | Allowance granted to the Pool contract. | | `results[].allowancePermit2` | string — decimal, raw units | Allowance granted to the Permit2 contract. Absent means either zero or not reported for that chain — the two are indistinguishable. | | `results[].error` | string | Set when this query could not be answered. | **Example** ```json // POST /swap/account/allowances {"queries":[{"chainId":103,"address":"0xb1Ce525A223DB37BbbC5636D1dd70f7bfeF6e3cD", "token":"0x24A11478F452Fb9474E0f8930eB58942F3f6Ef90"}]} // response {"results":[{ "chainId":103,"address":"0xb1Ce…e3cD", "token":"0x24A11478F452Fb9474E0f8930eB58942F3f6Ef90", "allowancePool":"115792089237316195423570985008687907853269984665640564039127584007913129639935", "allowancePermit2":"115792089237316195423570985008687907853269984665640564037223584007913119639935" }]} ``` --- ## 16. Flows ### 16.1 Single-chain, you pay gas | # | Call | Result | |---|---|---| | 1 | `GET /swap/config/all` | chains, assets, precisions | | 2 | `POST /swap/status` | amountTo, executionFeeNative, min/max/balance | | 3 | `POST /swap/create/singleChain` | orderId, maintainerSignature, nonce, deadline | | 4 | — | call the Pool contract, attaching executionFeeNative as native value | | 5 | `POST /swap/notify/singleChainStatus` | `{ orderId, status:"success", transactionId }` | | 6 | `GET /swap/singleChain/status?orderId=…` | poll until `"success"` or `"error"` | ### 16.2 Single-chain, gasless (EVM / Tron) | # | Call | Result | |---|---|---| | 1 | `POST /swap/create/singleChain` `{ gasLess: true }` | `method: "permit" \| "permit2" \| "signature"`, and the matching document: `permit2_typed_data` for `permit` / `permit2`, `user_auth_typed_data` for `signature` | | 2 | — | the user signs the typed data; no transaction, no gas | | 3 | `POST /swap/notify/userPermitSignatures` | `{ orderId, permitSignature \| userAuthSignature }` | | 4 | `GET /swap/singleChain/status?orderId=…` | poll | ### 16.3 Single-chain on Solana | # | Call | Result | |---|---|---| | 1 | `POST /swap/create/singleChain` `{ gasLess: true }` | `gasLessData`: base64 transaction, already signed by us and paid for by us; no `method` | | 2 | — | add the user's signature. Do not broadcast: the embedded blockhash expires about a minute after we build it, far sooner than `deadline`. Once expired, create a new order | | 3 | `POST /swap/notify/userSignedTransaction` | `{ orderId, signedTransaction }`. We broadcast it | | 4 | `GET /swap/singleChain/status?orderId=…` | poll until `"success"` or `"error"` | | # | Call | Result | |---|---|---| | 1 | `POST /swap/create/singleChain` `{ gasLess: false }` | maintainerSignature, nonce, deadline; no gasLessData | | 2 | — | build, sign and broadcast the call against our program, using `maintainerSignature`; ask us for the program interface | | 3 | `POST /swap/notify/singleChainStatus` | `{ orderId, status:"success", transactionId }`, `transactionId` being the base58 signature | | 4 | `GET /swap/singleChain/status?orderId=…` | poll until `"success"` or `"error"` | ### 16.4 Cross-chain, you pay gas | # | Call | Result | |---|---|---| | 1 | `POST /swap/create/crossChain` `{ …, sessionPubkey }` | secretHash, maintainerSignature, nonce, deadline | | 2 | — | lock funds in the source HTLC, attaching executionFeeNative | | 3 | `POST /swap/notify/userLockSourceTransaction` | `{ secretHash, transactionID }` | | 4 | `GET /swap/crossChain/status?secretHash=…` | wait for `destinationLockTransactionId` | | 5 | `POST /swap/validate` `{ secretHash, type:"lockDestination" }` | `valid: true` | | 6 | — | the session key signs EIP-712 `Claim{secretHash}` (§9) | | 7 | `POST /swap/notify/userSessionSignature` | `{ secretHash, sessionSignature }` | | 8 | `GET /swap/crossChain/status?secretHash=…` | poll until `"success"` | ### 16.5 Cross-chain, gasless | # | Call | Result | |---|---|---| | 1 | `POST /swap/create/crossChain` `{ gasLess: true, sessionPubkey }` | secretHash, method, `permit2_typed_data` (+ `user_auth_typed_data` for `"signature"`) | | 2 | — | the user signs the typed data | | 3 | `POST /swap/notify/userPermitSignatures` | `{ secretHash, permitSignature \| userAuthSignature }` | | 4 | `GET /swap/crossChain/status?secretHash=…` | poll | | 4a | `POST /swap/validate` `{ type:"lockSourceGasless" }` | `sourceLockTransactionId` appears | | 4b | `POST /swap/validate` `{ type:"lockDestination" }` | `destinationLockTransactionId` appears | | 5 | `POST /swap/notify/userSessionSignature` | `{ secretHash, sessionSignature }` | | 6 | `GET /swap/crossChain/status?secretHash=…` | poll until `"success"` | On Solana there is no typed data: step 1 returns `gasLessData` instead, and steps 2 and 3 become "sign it" and `POST /swap/notify/userSignedTransaction` `{ secretHash, signedTransaction }`. The rest is the same. ### 16.6 Order status | Value | Single-chain | Cross-chain | |---|---|---| | *absent* | — | in flight | | `initialized` | open, not yet confirmed | — | | `success` | executed and confirmed | claimed on both chains | | `error` | execution failed | swap failed | | `refunded` | — | the swap did not complete and funds were returned | ---