Moove API
One call. Paid in full.
Create a payment link from your code. Your customer pays in any token, and you receive the full amount in yours.
From key to first payment.
Create an API key
In Moove Business, create a key for the Moove Receive Agent. It’s shown once, so put it straight into your environment.Create a payment link
One POST returns a checkout URL. Your customer pays there, in any token, on any chain.Hear when it’s paid
Register an HTTPS endpoint, and Moove sends it a signed event the moment a link is paid.
Small API. Solid guarantees.
Any token in, yours out
Customers pay in what they hold, on 30+ blockchain networks. Every payment settles to your wallet, in the token and on the chain you chose.A contract you can build on
Versioned in the path, additive in v1, with a live OpenAPI schema.Clear limits, clear errors
Limits per key and per IP, a plain 429, and one error shape with stable codes.No charge for the API itself.
No subscription and no per-call charge. A customer paying in another token or on another network covers the 0.02%, so you receive the full amount.- API access
- Free
- Same token, same network
- Free
- Across tokens or networks
- 0.02%
Moove vs building it yourself.
| Moove vs building it yourself. | Moove | Building in-house |
|---|---|---|
| Chains covered | Moove: 30+, from one endpoint | Building in-house: One integration per chain |
| Converting to your token | Moove: Built into every payment | Building in-house: Your own swap and bridge routing |
| Knowing a payment landed | Moove: Signed webhooks and a list endpoint | Building in-house: Listeners you run for every chain |
| Checkout page | Moove: A hosted link, ready to share | Building in-house: Designed, built and hosted by you |
| If a key leaks | Moove: It can only request payments to you | Building in-house: Whatever the hot wallet holds |
Frequently asked questions.
How do I get an API key?
Sign in to the Moove Business console and open API keys. Name the key and choose the Moove Receive Agent, which grants permission to create and read payment links. The full key is shown once, at creation, and never again, so store it in a secret manager. There is no endpoint that creates keys, so one key can never issue another.
Where does the money go when a customer pays?
To the key owner’s default wallet, in that wallet’s chain and settlement token. The caller can’t name another destination. That is why the account needs a claimed Moove handle and a default wallet with a settlement token before the first call; without both, creating a link returns a 409 saying the account isn’t ready to receive payments.
Is there a payout API?
Not yet. The API receives payments; it doesn’t send them. To pay suppliers or contractors today, use Send in the Moove Business console. A Moove Send Agent has been announced and will appear in the docs when it ships.
How do Moove webhooks work?
Register up to five HTTPS endpoints in the console. Each receives two events: one when a payment against a link settles, and one when a link completes. Deliveries are signed with HMAC-SHA256 using a secret shown once. Delivery is at least once, so de-duplicate on the event id. A failed delivery is retried up to six times.
Are there rate limits?
Yes. Requests are limited per API key and per source IP, whichever is reached first, and going over returns 429. Back off exponentially with some jitter rather than retrying at once, because rejected requests still count. Use webhooks for payment status instead of polling a single link, and budget against the IP limit if several integrations share one host.
How is the API versioned?
In the path. Today there is one public version, v1. Changes inside a version only add: new endpoints, new optional fields, new response fields. Anything that would break a client, such as removing a field or changing a type, ships as a new path version. Build your client to ignore unknown fields and to branch on error codes, never on messages.
