Contact

Email is how you reach us

Three addresses, each going somewhere different. Pick the one that matches what you need and you will skip a forwarding step. There is no phone line and no chat widget — putting a number on this page that nobody answers would waste your afternoon, not ours.

Where to write

Pick the right inbox

Sales and support

Pricing, onboarding, whether this fits what you are building, and anything that is not working the way the docs say it should.

  • A quote for your volume and assets
  • Help with an integration that is misbehaving
  • Questions about your account or a specific payment
[email protected]

Security

Vulnerability reports and anything that looks like it could affect the safety of funds. This one is read with priority.

  • A vulnerability you have found
  • Suspected compromise of an account or a key
  • Anything about this system that worries you
[email protected]

Legal

Contracts, data protection requests, law enforcement correspondence and anything to do with the terms.

  • Contract and terms questions
  • Data protection and privacy requests
  • Formal or regulatory correspondence
[email protected]

Before you write

What to include

Not a form to fill in, just the things that let us answer in one reply instead of four.

If you are asking about pricing

  • Rough monthly volume

    An order of magnitude is enough. It is the main thing a rate depends on.

  • Which assets

    Bitcoin, Ethereum, Litecoin and Polygon are what exists today. If you need something else, say so — it is useful to know even when the answer is no.

  • How you would take payment

    Hosted links, the API, or both. It changes how much work onboarding is.

  • How you pay out

    One address occasionally, or a payroll of hundreds every month. Batch size drives fees more than anything else.

If something is broken

  • The payment request id

    The slug from the hosted page URL is the fastest way for us to find it.

  • What you called and what came back

    The endpoint, the status code and the response body. Please redact the API key.

  • When it happened

    With a timezone. Half of these turn out to be a scheduled job that ran between two events.

  • Never send us a secret

    Not your API key, not your webhook signing secret, not an authenticator code. We will never ask for any of them, and anyone who does is not us.

We have not published a response time. There is no support SLA on this page because none has been agreed, and quoting one we have not committed to would be a promise made by a marketing page rather than by a person. If your account needs a guaranteed response window, raise it while you are negotiating terms.

Already a customer?

Sign in to open your payments, balances and recent webhook deliveries before you write — the answer is often on the deliveries list.