Choosing a payment gateway means trusting it with the part of your business that matters most — the money. That trust should be earned with specifics, not slogans. So here's a straight account of how CryptoPayr handles your funds, your access and your data, and the lines we deliberately don't cross.
Your balance can't quietly go wrong
The most important property of a money system is that the numbers always add up. CryptoPayr enforces that at the database level. When you request a payout or a transfer, the amount is reserved atomically in a single transaction — so two actions can never spend the same dollars, and a balance can't be pushed negative. Funds only finalise when the processor confirms the money actually moved; if anything fails along the way, the reserve is released straight back to you. Settlement is driven by signed webhooks from the upstream network, not by hopeful guesses.
The processor is never exposed to buyers
Behind the scenes, CryptoPayr talks to a crypto processor to move funds on-chain. Your customers never touch it and never see it. The hosted checkout handles coin choice, rates and confirmations inline — there's no redirect to a third party where a buyer could be phished or confused. Every request and webhook between us and the processor is cryptographically signed, so a forged callback can't fake a payment into existence.
Access you control, scoped to what's needed
Security isn't only about our side — it's about giving you safe controls:
- API keys authenticate over bearer tokens and can be rotated whenever you need. Treat one as compromised? Replace it, and the old one stops working.
- Two-factor authentication (TOTP, with backup codes) protects your account login, so a leaked password alone isn't enough to get in.
- Signed merchant webhooks let your systems verify that a "payment completed" event genuinely came from us before you ship anything.
- Rate limiting and replay protection guard the API — including idempotency keys so a retried payment request can't accidentally charge twice.
Data handled with restraint
The whole site runs HTTPS-only; requests over plain HTTP are forced up to a secure connection. Database access is parameterised throughout, which closes the door on the injection bugs that leak customer data elsewhere. And crypto changes the data picture in your favour: a buyer can pay without handing over card numbers and a full billing identity, so there's simply less sensitive data sitting around to lose.
The boundaries we hold
Good security is also about saying no. We don't expose the processor to buyers. We don't let logging or notifications interfere with a money flow — if a Discord ping or an email fails, your payment still completes correctly. And we don't let convenience features override the rule that balances reconcile exactly.
None of this asks you to take our word for it — it's how the product is built to behave on every payment, payout and refund. If you want the operational and legal detail, our legal centre lays out the policies that sit alongside the engineering. Trust should come with receipts; this is ours.