StableRoute

In 2025, stablecoin monthly transfer volume increased to more than $5 trillion; and this trend is growing. However, many businesses still don't use stablecoins because of compliance, regulations, and complexity of UX.

😫 Problem: Businesses who have legal reasons to receive payments in crypto in their countries (Poland, Germany, Argentina, etc.) still don’t have solutions to implement in their businesses because:

• They need information about transfers for compliance;
• They must avoid receiving crypto from countries under the sanctions (North Korea,Russia, etc.);
• Crypto lacks core features businesses expect from payment providers, like canceling a payment or pulling it back if it isn’t confirmed.

🌎 Solution: StableRoute — a B2B stablecoin payment provider that tackles real-world pain points: compliance, user experience, misrouted funds, and eliminating complexity of bridges.

✅ Usecases we cover with StableRoute: ▸ We give a confirmation of from which country to which country a payment in USDC was made — for tax, accounting, and legal reasons. ▸ We help to avoid payments to wrong wallets due to copy-paste mistakes or opaque addresses. ▸ We allow users to cancel payments or pulling them back if it isn’t confirmed. ▸ Cross-chain payments typically require bridging — risky and confusing. Native multichain USDC routing without bridges is the solution.

🧑‍💻 Partners’ technologies we use:

Circle: USDC as the main stablecoin for global payments. Using USDC makes crypto payments more trustworthy. USDC multichain payment system makes StableRoute user friendly and secure.

Self: Identity verification by scanning a government-issued ID or passport. Self helps to avoid sending USDC to the countries on the sanctions list. Sender can be sure that the receiver is correct.

ENS: Corporate ENS to help avoid human factor of sending to incorrect name or wallet, and simplify UX. We use it like corporate email, where there is the main domain and are subdomains acting under the main one.

💡 The flow:

An administrator, functioning as an accountant, initiates the creation of a voucher allocated to a specific employee. The employee subsequently accesses the dedicated redemption user interface and performs self-verification utilizing their passport on Self. Following identity verification, the employee queries the primary digital vault to ascertain the availability of adequate USD for transaction execution. Should the primary vault contain insufficient funds, the employee is required to orchestrate a transfer of USDC from a secondary vault (residing on an alternate blockchain) to the primary vault via the CCTP protocol.

Upon successful USDC dispatch and availability in the primary vault, the payment is processed, and the voucher's status is updated to "closed." Conversely, should the employee fail to complete the redemption process within the stipulated timeframe, or if the provided passport identification fails to correspond with the voucher's embedded data, the voucher will be automatically invalidated, precluding its redemption by the employee.

📌 Voucher Arbitrum Sepolia: 0x7638B70a880Db6E632cC4F1F5aDB5a1a86E5043D

Vault Base Sepolia: "0xeDEe63D448f8f9e4237C159CaD7A427598F6d31c"

testcompany.eth (L2 integration) Arbitrum: "0x1035E9A680F6A7bF051C72e42DE70dB297bDB970"

Endpoint Self Celo: "0xa38e93cAaEC44B8D9d9CfaA902EC6B4782B0e3E1"