About

Stablecoin rails we would trust with our own money.

ZyntrixPay started as the deposit gateway we wanted to integrate: per-client addresses, confirmations that survive a reorg, callbacks that survive an outage. The same ledger, scanners and withdrawal controls now also power a P2P Exchange, so the people on the other side of those deposits can hold, send and trade stablecoins too.

Custody, on both products

Custody was the part nobody wanted to talk about

Every broker we talked to eventually asked the same question: who is holding the money between a deposit landing and a payout going out? We used to answer that with a purely non-custodial design. We do not run it that way anymore, and we would rather explain the change than let you find it in the terms.

ZyntrixPay now runs one platform wallet. Every client still gets a dedicated deposit address, generated and tracked for you automatically — the address is just derived from our key now, not yours. Deposits are credited to your balance the moment they confirm.

Getting funds out is a request, not an automatic transfer. You ask for a withdrawal through the API or panel, and someone on our side reviews and signs it before anything moves. That manual step is slower than a fully automated payout on purpose — it is the control that keeps a bug, or one compromised key, from being able to empty an account by itself.

The P2P Exchange is built on the same principle. Balances live on our ledger, withdrawals to an external wallet pass limit, identity and two-factor checks and can be held for review, and crypto in a P2P trade sits in escrow until the trade completes.

Straightforward about custody

We hold the platform wallet client funds settle into. That is a real change in what you are trusting us with, and we would rather say so plainly than have you find out from the terms of service.

Boring where it counts

Two networks, one asset, a dozen endpoints. Confirmation thresholds, reorg margins and retry policy get the attention instead of a feature list nobody asked for.

Honest about the trade-offs

Holding client funds is a bigger responsibility than watching addresses we could not touch. We keep visible controls around it — manual withdrawal review, a balance you can check any time — because a trust relationship deserves more than a promise.

Written for the engineer doing the work

The integration guide covers reorg handling, idempotency semantics and a full error reference — because the person integrating us needs answers, not a brochure.

Security

What protects the account, the treasury and the callback

Custody depends on our controls, not just the cryptography. Here is what stands between a deposit and a withdrawal on the Merchant Gateway, and what protects the account and the API. For wallet users, see how the P2P Exchange is secured.

Withdrawals need a person

No API call moves funds out on its own. Every withdrawal request is reviewed and signed by someone on our team before it broadcasts — the biggest single control against a bug or a compromised key.

Mandatory two-factor

The merchant panel stays locked until two-factor authentication and a verified email address are both in place. There is no way to opt out and run without them.

Signed, time-boxed requests

Every API call carries an HMAC-SHA256 signature over the timestamp, method, path and body hash, valid within a ±300 second window. Replays and tampered bodies never reach a handler.

Verifiable callbacks

Webhooks are signed with Ed25519. The public key is published at a public endpoint so your server can verify every delivery independently — and verification is mandatory, not advisory.

Rate limiting and backoff

120 requests per minute per API key, answered with 429 and a Retry-After header rather than a silent drop, so your client can back off correctly.

Reorg-resistant crediting

Confirmations are counted against a threshold you choose, and the scanner stays a deliberate margin behind the chain head. A rollback reverses cleanly instead of leaving you credited for money that vanished.

Found something? Security reports go to security@zyntrixpay.com. We read every one, we will confirm receipt, and we will not take action against anyone reporting a genuine issue in good faith.

Contact

Let’s talk

Integrating the Merchant Gateway? Tell us what you are running and roughly what you process, and we will come back with a rate and a recommended integration model. Questions about the P2P Exchange or becoming a verified P2P maker are welcome here too.

Sales & onboarding sales@zyntrixpay.com
Technical support support@zyntrixpay.com
Security disclosure security@zyntrixpay.com

Send us a message

We reply within one business day.

We use what you send here to reply to your enquiry, and nothing else.