Documentation
Introduction
What JuicePay is, the problems it removes, and how the pieces fit together.
JuicePay is an API and dashboard for moving stablecoins and other digital assets between chains, accounts, and counterparties. It exists because settlement onchain is reliable but tedious: every network has its own finality rules, every venue its own pricing, and every retry its own way of duplicating a payment.
We take that tedium on. You get one balance, one ledger, and one status webhook that tells you what actually happened.
What you can build#
- Checkout — accept stablecoins from customers on the chain they hold, and settle in the asset you prefer.
- Payouts — pay contractors, vendors, or a whole payroll run in a single signed batch.
- Treasury — consolidate balances held across many chains and entities into one position.
- Conversion — quote and execute swaps between stablecoins and majors, including limit orders.
How the pieces fit#
A request normally travels through four stages:
- Intent — you create a resource describing what you want, such as a payment intent or a payout batch. Nothing moves yet.
- Authorisation — policy checks run against your account rules, and required approvals are collected.
- Execution — JuicePay signs and broadcasts the necessary transactions, routing each leg across whichever network is cheapest and fastest at that moment.
- Confirmation — the resource reaches a terminal state, and a signed webhook tells you which one.
Because stage four is a webhook rather than a polling loop, your integration does not need to guess how long a chain will take. It needs to handle an event.
Environments#
Every account starts with a sandbox environment. Sandbox behaves identically to production at the API surface but settles against deterministic fixtures, so tests never flake because a network was congested.
| Environment | Base URL | Purpose |
|---|---|---|
| Sandbox | https://api.sandbox.juicepay.test | Development and automated tests |
| Production | https://api.juicepay.test | Live value movement |
Keys are environment-scoped. A sandbox key is rejected by production and vice versa.
Where to go next#
- Follow the Quickstart to move your first dollar.
- Read Accounts and balances for the data model.
- Skim Idempotency before you write any retry logic — it will save you an incident later.