Skip to main content
Version: 0.3.0

International payment flows

Run fast, cheap, cross-border payment flows — payroll, creator payouts, multi-merchant payment gates — using encrypted rails, so that neither competitors nor your own network participants can read each other's volumes, transaction sizes, or the terms you offer them.

The problem​

Crypto makes complex payment flows easy to orchestrate: multiple counterparties, custom routing logic, multiple jurisdictions, settlement in seconds. But every public-chain flow leaks data — and a multi-party flow leaks it to two distinct adversaries.

  • Competitors read your business off the chain — assets you hold, total volume, payroll size, customer concentration. Same threat as any treasury or custodial operation.
  • Your own participants read each other. A merchant on your payment platform can look up the volumes other merchants do. An influencer can see the rates a brand pays other influencers. An employee can compare salaries against their coworkers. And every participant can read the terms you offered them versus the terms you offered everyone else — fees, rates — all visible on the public ledger.

Existing private on-chain alternatives don't compose well across counterparties, asset types, and jurisdictions, and they push regulatory risk back onto the operator.

What stays private​

In a multi-party flow on encrypted balances, neither the public nor your network participants can read:

  • Volumes per counterparty. What you paid to whom.
  • The terms you offered each participant — fees, rates.
  • Transactions of any single participant. All balancs and amounts are encrypted.
  • Flow size. Your total volume, mertics of your partners.

Connecting the flow​

Payment flows are modular. Encrypted balances slot in at every stage:

  • Input. Fiat via our partner on-ramps in multiple currencies and jurisdictions, or crypto (USDC, other stablecoins, public-chain assets) from any wallet your participants already use.
  • Platform. Self-custodial wallets for participants who hold their own keys; custodial wallets for accounts you operate (escrow, treasury, settlement pools); or both, in the same flow.
  • Output. Any supported ZK stable, with built-in swap to land the flow in a different asset; or fiat via partner off-ramps in the recipient's currency and jurisdiction.
  • Operator rail. As an issuer partner, you get 1:1 fiat ↔ ZK stables at no cost under MiCA — encrypted rail for funding large flows and reconciling at scale.

A flow can mix all of these: fiat in from one country, encrypted routing across self-custody and custodial accounts, fiat out in another country in another currency. None of it leaks to anyone outside the flow.

Where this fits​

  • International payroll. Employer funds in one currency via the MiCA rail; salaries route to employee self-custodial wallets; employees off-ramp locally. No employee sees another employee's salary; no competitor sees your total payroll.
  • Creator and influencer payouts. Brand pays creators across borders with per-creator terms; no creator sees another creator's rate; no competitor sees your campaign budget or creator network.
  • Multi-merchant payment gates and marketplaces. Customers pay in, you settle out to merchants in their preferred currency and asset. Merchants can't read each other's volumes or the fees you negotiated with each of them.

Built for production UX​

The underlying SDK is built for the platforms a payments product actually ships on:

  • Mobile and web. First-class support for both participants and operator dashboards.
  • Fast transactions. Settlement in seconds; no UI blocking on proof generation.
  • Gas abstraction. Recipients don't need to hold ETH; fees can be sponsored by the operator or paid in the asset already held.

Privacy properties​

The public sees only that encrypted accounts exist and that transfers happen between them — never amounts, counterparties, or terms.

Each participant sees only what passes through their own account: their salary, their payout, their settlement. They cannot read other participants' accounts or activity.

The operator sees the full flow — all accounts under their keys, all routes, all terms — and can grant view-keys to auditors, regulators, and tax authorities under whatever regime applies.