Eleven chains, one balance
Receive on Base, Arbitrum, Solana, Ethereum, Polygon and more. Your counterparty picks the network; you see a single consolidated position.
Move stablecoins across chains, pay thousands of recipients in a single signed batch, and reconcile everything in one ledger. Programmable treasury for teams that treat settlement as infrastructure — not an afterthought.
Settle in 24 assets
SOC 2 Type II · MPC custody
Total balance
$312,904.18
USD Coin
USDC
184,320.55
+2.4%
Tether USD
USDT
96,110.02
+0.1%
Ether
ETH
412.88
+5.9%
Solana
SOL
9,204.10
−1.2%
5 of 11 chains synced
Moving money for teams of every size
Your assets, your way
From a two-person studio paying three contractors to a treasury desk dispatching a hundred thousand legs a week — the primitives are the same, only the limits change.
Your assets, your way
Hold and receive across eleven networks from a single balance sheet. Counterparties pay on whichever chain suits them — you reconcile in one ledger, in the asset you actually want to keep.
Receive addresses
Sweeping0x7f…4a1c84,210.440x7f…4a1c52,004.100x7f…4a1c218.910x7f…4a1c14,402.00Consolidated to USDC every 6 hours
In flight
$1,284,902
Borderless by default
Networks do not keep business hours and neither do we. Dispatch to any address on any supported chain and get a definitive status — accepted, settled or refunded — without chasing a support ticket.
Unified ledger
Every chain rolls into one balance sheet and one reconciliation file.
Smart routing
Each transfer picks the cheapest credible path by cost and finality.
Onchain proof
A verifiable transaction hash for every leg, exportable with your reports.
Gas sponsorship
Your recipients need no native token to receive what you send them.
Exchange without stress
Stop juggling four dashboards and a spreadsheet. Quote, convert and settle inside JuicePay, with the depth of seven venues behind every fill.
Guaranteed execution
A quote is a commitment. If depth moves out from under it, we re-quote automatically and tell you why.
Multi-pair liquidity
Stablecoin triangles, majors and regional tokens — routed across venues so your size never moves the price alone.
Transparent pricing
Network cost at raw gas, platform fee shown as a line item, zero markup buried in the rate.
Convert
Live venue rateYou send
You receive
Aggregated depth · USDC/USDT
12bps effective spreadLimit order
WorkingYour money, your rate
Set the rate you are willing to accept and walk away. JuicePay watches the venues, executes the moment your target prints, and notifies you either way.
No slippage surprises
Orders only fill at or better than your stated rate.
Capital stays yours
Funds remain in your account until the order executes — never locked in a venue.
Cross-chain execution
Quote in one asset, settle in another, on whichever network you prefer.
Partial fills allowed
Take the order in tranches when depth is thin instead of forcing one large print.
Pairs settle across 6 regional stablecoins
Built for operators
Fewer fees, fewer manual steps and a paper trail that satisfies your auditors the first time they ask.
Receive on Base, Arbitrum, Solana, Ethereum, Polygon and more. Your counterparty picks the network; you see a single consolidated position.
Network cost passed through at raw gas, never marked up. Zero platform fee on stablecoin pairs and internal transfers.
Multi-party approvals, per-recipient allowlists, hardware-backed signing and an immutable audit log for every movement.
Deterministic retries, idempotent calls and a status webhook for every state change. You always know where a payment is.
No card required. Sandbox keys are issued instantly.
Online and in person
Offer the chains and assets your customers already hold. We absorb the volatility and the network complexity, then hand you a single balance in the asset you choose.
Hosted checkout you can ship in an afternoon
Embeddable widget for existing storefronts
Automatic refunds and partial captures
Invoice reconciliation by your own reference ID
Orchard Labs
Invoice INV-2291
4,250.00 USDC
juice.link/inv-2291Non-custodial settlement · verified merchant
Accepted on checkout
Settlement asset is your choice — customers never see it.
Our solutions
Four ways teams put JuicePay to work, each one deployable on its own or stacked into a complete treasury stack.
Move value between networks without exposing your team to bridge risk. Routes are selected per transfer for cost and finality, then proven onchain.
See every chain, wallet and counterparty in one position. Set target allocations and let policy-based rebalancing keep your runway intact.
Accept stablecoins at checkout with hosted or embedded flows. Settlement lands in your JuicePay balance while the customer stays on the chain they prefer.
Consolidate revenue held across regional entities and chains back to your main treasury, with a full audit trail for each hop.
Security you can audit
JuicePay never holds a complete private key. Signing authority is split across independent parties, and every movement is attributable to a named human and an immutable log entry.
MPC key custody
No single device or operator can authorise a transfer alone.
Hardware-backed signing
FIPS 140-2 Level 3 modules with attested firmware.
Policy engine
Velocity caps, allowlists and approval quorums per account.
Continuous audit
Exportable logs feeding directly into your SIEM.
POST /v1/webhooks · live
payment_intent.succeeded0.42spayout.batch.accepted0.61sswap.quote.locked0.18swebhook.delivered0.09s{
"id": "pi_9fK2xQ",
"amount": "4250.00",
"asset": "USDC",
"chain": "base",
"status": "succeeded"
}For developers
Idempotent by default, versioned without ceremony, and documented with runnable examples in the languages your team already writes.
REST endpoints with cursor pagination
Signed webhooks with replay windows
TypeScript, Go and Python SDKs
Deterministic sandbox fixtures
GET /v1/balances{
"object": "balance",
"asset": "USDC",
"available": "312904.18",
"chains": ["base", "solana", "arbitrum"]
}Latest from our blog
A twelve-second transfer that can be reorganised is slower than a forty-second one that cannot. Here is how we model finality risk before routing a payout.
· 7 min read
What happens when a client retries a batch four times because a webhook was slow? A walk through the keying strategy behind our payout primitives.
· 9 min read
Matching your internal books to chain state is mostly a schema problem. We share the event model we settled on after three rewrites.
· 6 min read
Get started
Open an account, mint a sandbox key and ship your first payout today. No sales call required — though we are happy to take one.
Eleven chains · 24 assets · one balance