> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypermid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get an account

> How to get onboarded, and what you receive when you are.

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 — which
merchant account payouts land in, so it starts with a conversation rather than
a signup form.

## Ask for an account

Email **[support@hypermid.io](mailto:support@hypermid.io)** with:

<AccordionGroup>
  <Accordion title="Who you are">
    Company name, your website, and the country you operate from.
  </Accordion>

  <Accordion title="What you want to build">
    Which of the four products you need — [checkout](/guides/checkout),
    [deposit](/guides/deposit), [withdrawal](/guides/withdrawal),
    [swap](/guides/swap). You can add more later; naming them up front just
    means your keys work on day one.
  </Accordion>

  <Accordion title="Where funds should land">
    The chains and tokens you want to settle in. If you already know your
    payout addresses, send them — checkout destinations need an ownership
    signature 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.
  </Accordion>

  <Accordion title="Whether you need fiat">
    Card and bank payments settle into **your own** merchant account with our
    onramp provider, not a pooled one. That needs separate credentials per
    environment, so say so early if you want it — it is the longest lead time
    in onboarding.
  </Accordion>
</AccordionGroup>

## What you get

<Steps>
  <Step title="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](/environments).
  </Step>

  <Step title="A dashboard login">
    [partner.hypermid.io](https://partner.hypermid.io) — magic-link sign-in, no
    password. Manage webhook endpoints, watch sessions, read your fee earnings.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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.

<Note>
  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.
</Note>

## Getting help later

Same address — **[support@hypermid.io](mailto: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.