Skip to main content
Hypermid accounts are created by us, not self-serve. Partner onboarding decides which products you can use, what your fee split is, and — for fiat — where settlements should land, so it starts with a conversation rather than a signup form.

​
Ask for an account

Email support@hypermid.io with:
Company name, your website, and the country you operate from.
Which of the four products you need — checkout, deposit, withdrawal, swap. You can add more later; naming them up front just means your keys work on day one.
The chains and tokens you want to settle in. If you already know your payout addresses, send them — checkout destinations need the portal’s emailed verification step before they can be used, so getting them registered early removes a step. Withdrawal recipients are supplied per session and are not added to this checkout allowlist.
Card and bank payments use Hypermid’s configured onramp account. Sandbox and production are separate provider tenants with separate credentials, and the settlement destination is set per order. Say so early if you want fiat — it needs its own environment configuration.

​
What you get

1

Sandbox access, immediately

A test key (sk_test_…) that works against testnets only. Nothing about it touches real money, so you can integrate fully before any commercial conversation concludes. See Environments.
2

A dashboard login

An administrator emails you a one-time setup link to partner.hypermid.io. Open it to choose and confirm a password, enroll an authenticator by scanning the QR code and entering its 6-digit code, save the one-time recovery codes, and finish the setup. The link is consumed when setup finishes; it is not your sign-in link. Afterwards, sign in with your email, password, and authenticator code (or a recovery code). Once signed in, your profile lets you optionally add a passkey for faster sign-in; password plus authenticator remain available. Manage webhook endpoints, watch sessions, and read your fee earnings from the portal.
3

Production access, once enabled

Live keys (sk_live_…) are issued only after your account is approved for production. Until then a live key request simply fails — sandbox keeps working throughout.

​
Payments fees

Payments has two fees on the same payer-input amount: Hypermid’s fee and your optional developer fee. Your developer fee defaults to 0 and can be set from 0 to 100 basis points in the partner dashboard; a positive rate requires your fee recipient. If Hypermid configures a partner-specific Hypermid rate, that override replaces the global rate outright — it is not added to or clamped by the global rate. Developer-fee settlement depends on the rail. On EVM routes, the combined fee lands with Hypermid; your leg is a balance owed to you and settled periodically by manual transfer. On Near deposit-address routes, your developer leg is paid directly to your configured recipient by the provider.
Sandbox and production are separate on purpose. A sandbox key cannot reach a mainnet chain even if you ask it to, so there is no configuration mistake that turns a test integration into a real payment.

​
Getting help later

Same address — support@hypermid.io. When reporting a problem with a specific request, include the traceId from the error response. It is how we find your exact call in our logs, and it turns a day of back-and-forth into one lookup.