Skip to main content
Hypermid lets a payer settle in whatever token they already hold, on whatever chain they hold it, while you receive one specific token on one specific chain. The swap and the bridge are ours to worry about.

​
One Payments product, three modes

Payments

Choose Checkout, Deposit, or Withdrawal by where the money is going.

Swap orchestration

Price any pair across chains and hand the user an executable transaction.
Payments has three modes — Checkout, Deposit, and Withdrawal — represented by the same payment-session object. They differ by who pays whom, not by a separate product engine. Payment links are the no-backend delivery path for a fixed-price Checkout; they are not a fourth mode. Swap orchestration is the odd one out: no session, no custody, no webhook. You quote a route and your user’s own wallet executes it.

​
The shape of an integration

1

Create the session on your server

POST /v1/payments/{mode} with your secret key. Never from a browser — see Authentication.
2

Send the payer to the returned URL

The response carries a hosted page at pay.hypermid.io. Redirect to it, or embed it with the SDK.
3

React to the result

Subscribe to a webhook. Treat the webhook as the trigger and a session read as the truth.

​
Before you start

Get an account

Onboarding runs through support@hypermid.io.

Sandbox first

sk_test_ keys reach testnets only. No real money can move.

Try the API

Interactive playground on every endpoint.
Amounts are base units, as strings — 10 USDC at 6 decimals is "10000000". Strings because an 18-decimal amount exceeds the IEEE-754 safe integer range, so parsing it as a JSON number silently loses the low digits. Parse with a bigint, never parseFloat.