Product and safety / Safety
Security and compliance
What protects the user's coins, what Maxy can and cannot do, and what stays with you.
What the user signs. One message binding the paying wallet, the coin, the sats, the price and its band, the solver's bond, the Bitcoin script that must receive the BTC, and the deadline.
An escrow has four exits.
| Exit | To | When |
|---|---|---|
| Settle | the solver | it proves it paid the BTC, with the required confirmations |
| Cancel | the user | no solver committed: the user any time, anyone after 2 hours |
| Slash | the user, plus the bond | a solver committed and did not prove within 144 blocks |
| Refund | the user | the Bitcoin deadline passed with no bond |
No escrow can be trapped: pausing never blocks refunds.
What proves payment. The verifier, an on-chain Bitcoin light client, checks proof of work itself. No Maxy server can mark a payment as made.
| Maxy can | Maxy cannot |
|---|---|
| Quote, and decline to fill | Move an escrow except as above |
| Upgrade the settler: a 48-hour timelock on Base, Arbitrum and Robinhood Chain, no delay on BNB Chain and Avalanche | Stop a user taking an expired escrow back |
| Revoke your key | Sign for the user or change what was signed |
Over HTTP without the SDK, compute the signing hash yourself and simulate before sending. The SDK does both. Full list: the integration guide PDF.
Compliance
Maxy holds no user funds and performs no identity checks. Maxy Mint's direct custody is the exception, and says so on its own page.
| Maxy | |
|---|---|
| Holds user funds or keys | No |
| Keeps identity data | No. Orders over the API keep no account. The SDK's swap.createOrder signs a selling wallet in, which creates a wallet profile |
| Performs identity checks | No |
| Screens recipient addresses | No |
| Stores | Per order: the signed intent, signatures, payout script, status. Per call: operation, time, IP address and key |
What stays with you.
- Your onboarding and identity checks, where your licences require them.
- Address screening, where your policy requires it, before you quote.
- Your users' records:
orderId, both addresses, amounts and hashes. - Your terms with your users, including who they contact for support.
No order is declined for a screening or jurisdiction reason today. externalCustomerId carries your own reference on an order. GET /addresses/validate checks form and network only.
Keep keys and webhook secrets in your server's secret store. Report an incident to your Maxy contact. SOC 2, a pen test letter and a signed SLA are not available. Vendor questions: the integration guide PDF.