White-label
Your own crypto payment gateway, in your own infrastructure
The same stack that powers PayKrypt, deployed inside your environment, under your brand, with the keys held by you. Self-custodial like BTCPay Server, but multi-chain from the first day, with subscriptions, invoicing, a merchant dashboard, and a team on call when something breaks at 3am.
Who this is for
Some businesses cannot use a hosted gateway, and the reason is rarely price. A marketplace needs to split a single incoming payment across many sellers on its own schedule. A gaming operator needs to pay out to a player address that has never been seen before, thousands of times a day, without a human approving each one. A regulated business needs customer data to stay inside its own perimeter.
On a hosted, custodial gateway, none of those are configuration problems. They are structural: the provider holds the funds, so the provider sets the payout policy. White-label removes the provider from that position entirely.
- Marketplaces and platforms that need to settle to many sellers from one payment, on rules only they can define.
- Gaming and iGaming operators who need unattended, high-volume payouts to arbitrary player addresses.
- Businesses whose licence, jurisdiction, or auditors require that customer and transaction data never leave their infrastructure.
- Payment providers and PSPs who want to offer crypto under their own brand rather than reselling someone else’s.
Self-custodial, and what that actually means
Keys are generated in your environment and stay there. PayKrypt does not hold your funds, cannot move them, and cannot freeze them. There is no PayKrypt balance page between a customer paying you and you having the money, because there is no PayKrypt in the middle.
This is the same trust model as BTCPay Server, and it has the same consequence: custody is your responsibility. You choose the wallet architecture, the signing policy, and who can approve what. We help you design it and we will tell you plainly when a choice is a bad one, but the keys are yours.
It also changes your regulatory position. A provider that holds crypto on your behalf is performing custody, which is what triggers authorisation regimes like MiCA’s CASP requirements in the EU. Software you run yourself, holding your own funds, does not put a licensed intermediary in your payment flow. Take that as the reason to have the conversation with your own counsel, not as legal advice from us.
Payouts on your terms, not ours
This is the single biggest difference from the hosted product. On hosted PayKrypt, a payout goes to a pre-whitelisted address and whitelisting requires interactive approval, which is the right default when someone else is holding your money.
In your own deployment, that policy is yours to set. Pay out to an address the moment your system decides to, with velocity limits, approval thresholds, and signing rules you configure against your own risk appetite rather than ours.
That is what makes marketplace settlement and player withdrawals workable. We are not claiming a hosted feature you have been waiting for. We are handing you the rails and getting out of the way, so the settlement logic your business needs is yours to write.
What gets deployed
A complete gateway, not a payment button. The stack that runs on paykrypt.io is the stack you get.
- Payments API: payment intents, invoices, subscriptions with trials and coupons, donations, refunds, and payouts.
- Hosted checkout: the customer-facing payment page, on your domain and in your brand.
- Merchant dashboard: balances, transactions, customers, products and prices, API keys with scoped permissions, and MFA.
- Customer portal: self-service subscription management for your end customers.
- Chain infrastructure: deposit address derivation, confirmation tracking, and withdrawal execution across the supported chains.
- Webhooks: signed, retried with escalating backoff, with a delivery log you can inspect.
- Double-entry ledger: every balance movement is a journal entry, so the books reconcile and your auditors have something to read.
Multi-chain from day one
BTCPay Server is excellent, and it is Bitcoin-first: everything beyond it depends on plugins of varying maturity. If your customers pay in USDT on Tron, that difference decides the project.
PayKrypt is multi-chain in its core data model rather than through extensions. Bitcoin, Ethereum, Base, Tron, BNB Chain, Polygon, Solana, XRP Ledger, and TON, with the major stablecoins on the chains that carry them. Adding an asset is configuration, not a fork.
Everything BTCPay leaves you to build
Running your own gateway usually means the payment part is solved and the commerce part is not. A self-hosted Bitcoin node will happily accept a payment; it will not tell you that a customer’s subscription lapsed, chase an overdue invoice, or apply a coupon for three cycles and then stop.
Those are the parts that take a year to build and never stop needing maintenance, and they are included here.
- Native subscriptions: trials, coupons, per-cycle invoicing, dunning on unpaid cycles, and a self-service customer portal.
- Invoicing: itemised invoices, branded PDFs, a public pay-by-link page, and automatic overdue reminders.
- Store integrations: the WooCommerce plugin and WHMCS module, pointed at your deployment instead of ours.
- Operational tooling: an admin surface, delivery logs, and a ledger that reconciles.
Supported, updated, and not your problem to maintain
The usual objection to self-hosting is that you inherit an operations burden and a security surface with nobody to call. That is a fair objection to most open-source gateways.
Deployments come with 24/7 support and a maintained upgrade path: security patches, chain upgrades and forks, new assets, and new platform features delivered to your deployment rather than left for you to backport. You run the infrastructure; you are not alone in it.
We will also help you get it standing up in the first place: environment review, deployment, wallet architecture, and an integration walkthrough with your engineers.
How an engagement runs
Every deployment is scoped, because a marketplace settling to two thousand sellers and an operator running player withdrawals do not need the same architecture.
- Scoping: your chains, assets, volumes, custody model, and regulatory constraints.
- Deployment: stood up in your cloud or on your hardware, on your domains, in your brand.
- Integration: your engineers build against the same public API and webhooks documented at docs.paykrypt.io.
- Handover and run: monitoring, upgrades, and 24/7 support once you are live.
Commercials
White-label is licensed and scoped per deployment rather than priced from a table, because infrastructure footprint, chain coverage, and support expectations vary enormously between customers.
If you are weighing it against the hosted product: hosted charges a percentage of what you process and we carry the operations and the custody. White-label moves both to you, which tends to make sense once volume is high enough that a percentage is the wrong shape, or when custody and data residency are non-negotiable regardless of volume.
FAQ
How is this different from BTCPay Server?
Same trust model, self-hosted and self-custodial, with three practical differences: it is multi-chain in the core rather than Bitcoin-first with plugins; it includes the commerce layer (subscriptions, invoicing, dunning, customer portal, merchant dashboard) rather than just payment acceptance; and it comes with 24/7 support and a maintained upgrade path instead of community support.
Does PayKrypt ever hold our funds?
No. Keys are generated in your environment and remain there. PayKrypt cannot move or freeze your funds, and there is no intermediary balance between your customer paying and you holding the money.
Can we do marketplace split payments and vendor settlement?
Yes, and honestly: we give you the payout rails and the ledger, not a turnkey split-payment product. Because you hold the keys and set the payout policy, you can implement settlement rules the hosted product cannot offer, which is the point of running it yourself. We will help you design it during scoping.
Can we run unattended player withdrawals for a gaming platform?
Yes. Payout policy is yours to configure, so payouts to previously unseen addresses can run automatically under velocity limits and signing rules you set, rather than requiring the interactive whitelist approval the hosted product enforces.
Does customer data stay in our infrastructure?
Yes. The database is yours. Customer records, transactions, and any KYC data you hold live in your environment and are subject to your retention and residency policy.
What does this mean for our regulatory position?
Self-custodial software you run yourself does not place a licensed custodian in your payment flow, which is what triggers regimes such as MiCA CASP authorisation in the EU. Your own obligations depend on your business, licence, and jurisdiction, so treat this as a reason to talk to your counsel rather than as legal advice.
Which chains and assets are supported?
Bitcoin, Ethereum, Base, Tron, BNB Chain, Polygon, Solana, XRP Ledger, and TON, with the major stablecoins on the chains that carry them. Coverage is configuration rather than a code fork, so additions are scoped with your deployment.
Do the WooCommerce and WHMCS integrations work with our deployment?
Yes. Both have configurable API and checkout base URLs, so they point at your deployment instead of PayKrypt’s.
How long does deployment take?
It depends on chain coverage, custody design, and your infrastructure, so it is scoped rather than quoted up front. Talk to us with your volumes and constraints and we will give you a real timeline instead of a marketing one.
Next steps
Start with the public Quickstart, then contact PayKrypt if you need help evaluating your integration path.