Your own payment gateway, under your brand
One API key gives you every payment method, cards and crypto, and a ready-made checkout with no brand on it. You set your margin; each payment is split on-chain between the merchant, you and anyone you resell through.
2% platform feeCards and cryptoPaid on-chain at once7 shop plugins
A 100 € payment
split on-chain, at once
Merchant
93.00 €
93%
Your partner
3.00 €
3%
You
2.00 €
2%
Platform
2.00 €
2%
Example with two resale levels: you take 2%, your partner takes 3%. Every wallet is paid with the payment.
Overview
How it works
You create a payment with your key. The buyer pays on the checkout. The amount is split and paid at once.
One key
Serves any number of merchants. The merchant's wallet is given on each payment.
Paid at once
Each payment is split on-chain when it is confirmed. Nothing is held.
Cards and crypto
Card methods and direct crypto (USDT, USDC, ETH, BNB… on 7 networks) on one page.
Your domain
Paste one file into Cloudflare: API and payment pages run under your name.
- 1You call
POST /v1/paymentswith the amount, the wallet of the merchant, and the list of wallets that take a share. - 2You receive a
checkout_url. The buyer sees the payment methods that work in their country, in their language. - 3When the payment is confirmed it is split on-chain: the merchant and every wallet in the list are paid at that moment, and your
callback_urlis notified.
Keys are issued on request
Tell us your brand, your website, what you sell and your expected volume. You receive a live key, a test key, a notification secret and the address of the API.
Pricing
Fees and sharing
The platform keeps 2% of each card payment, and less on crypto payments. Everything else is yours to decide.
| Who | Share | Set by |
|---|---|---|
| Platform, card payments | 2% (200 bps) | Fixed |
| Platform, crypto payments | A reduced share, given with your key | Fixed |
Each wallet in splits | Its bps (100 bps = 1%) | You, and each reseller level for its own share |
| Merchant | The rest | Automatic |
| Rule | Value |
|---|---|
| When shares are paid | On-chain, with the payment, as soon as it is confirmed. Nothing is held |
| Buyer pays in crypto | The lower platform share applies; your share and every reseller's stay the same. fees in the API shows it |
| Asset | The one the payment method delivers, same asset and network for every wallet |
| Wallets on one payment | 20 at most, all levels together. Each one is one more on-chain transfer |
| Total of all fees | 30% at most, platform fee included |
Quick start
First payment
One call creates a payment and returns the page where the buyer pays.
curl -X POST https://YOUR-API-ADDRESS/v1/payments \
-H "Authorization: Bearer wl_live_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: INV-2041" \
-d '{
"amount": "100.00",
"currency": "EUR",
"merchant_wallet": "0xMERCHANT...",
"splits": [
{ "wallet": "0xYOU...", "bps": 300, "label": "my margin" }
],
"order_ref": "INV-2041",
"callback_url": "https://your-site.com/hooks/payments"
}'YOUR-API-ADDRESS is the address you receive with your key. Redirect the buyer to checkout_url; you are notified on callback_url and can read the payment at any time.
Reference
API
Every call carries Authorization: Bearer <your key>. Bodies and answers are JSON.
| Call | Purpose |
|---|---|
POST /v1/payments | Create a payment |
GET /v1/payments/{id} | Read a payment and its status |
GET /v1/providers | Payment methods offered now, with their minimum amounts |
GET /v1/balances/{wallet} | What a wallet in splits has received so far |
| Field | Required | Meaning |
|---|---|---|
amount | Yes | Amount as text, two decimals: "49.90" |
currency | Yes | Three-letter code: EUR, USD, GBP… |
merchant_wallet | Yes | Wallet of the merchant who receives the payment, minus the fees |
splits | No | List of { wallet, bps, label }: who takes a share, and how much |
provider | No | multihosted (default: the buyer chooses among the best methods for their country, crypto included), crypto (crypto only), or one method from GET /v1/providers |
order_ref | No | Your own reference, returned in every answer and notification |
callback_url | No | Public https address notified when the status changes |
customer_email | No | Prefills the buyer's email on methods that ask for it |
metadata | No | Your own data, returned as it is |
Statuses of a payment
| Status | Meaning |
|---|---|
pending | Waiting for the buyer |
processing | Payment seen, being confirmed |
paid | Confirmed and split on-chain |
expired | Not paid in time |
Error codes
| HTTP | Code | Meaning |
|---|---|---|
| 400 | invalid_request | A field is missing or malformed; the message names it |
| 400 | invalid_splits | A split has no valid wallet, or bps is not a whole number |
| 400 | too_many_splits | More than 20 wallets share the payment |
| 400 | fees_too_high | The total of the fees is above 30% |
| 400 | amount_out_of_range | Below what the payment method accepts |
| 400 | provider_unavailable | Method not offered; use multihosted or another one |
| 401 | unauthorized | Unknown or missing key |
| 403 | key_suspended | The key is suspended |
| 404 | not_found | Unknown payment |
| 429 | rate_limited | Too many calls; wait and try again |
Send an Idempotency-Key header with your own reference when you create a payment: a repeated call returns the same payment instead of a second one.
Webhooks
Notifications
When a payment changes status, your callback_url receives a signed POST.
{
"type": "payment.paid",
"created": 1794046320,
"data": {
"id": "pay_8Hq2mZx4LrT6bN0cVw3K",
"status": "paid",
"amount": "100.00",
"currency": "EUR",
"order_ref": "INV-2041",
"tx_hash": "0x5c1e...",
"paid_at": "2026-11-19T10:19:41.000Z"
}
}| Point | Detail |
|---|---|
| Events | payment.paid, payment.expired |
| Signature | Header X-WL-Signature: t=<seconds>,v1=<signature>, HMAC-SHA256 of t.body with your whsec_… secret |
| Your answer | Any 2xx within 10 seconds. Otherwise it is sent again, eight times over about two days |
| Duplicates | The same event can arrive twice: use data.id to process it once |
Never deliver on a notification you have not verified. When in doubt, read the payment with GET /v1/payments/{id}.
Your domain
Resell under your own domain
Paste one file into Cloudflare and your domain becomes your own payment service: the API and the payment pages, nothing else. It never holds or moves money.
Shop
plugin or API
Reseller's domain
+ 3%
Your domain
+ 2%
Platform
+ 2%
1. Make your file
Prefer to edit it yourself? Download the plain file and change the four values at the top.
2. Put it on Cloudflare, then share your domain
- 1Cloudflare (the free plan is enough): Compute → Workers & Pages → Create application → Start with Hello World → Deploy → Edit code. Replace the code with your
worker.jsand press Deploy. - 2Worker → Domains → Add Domain: the address you want, for example
pay.your-domain.com. Cloudflare creates the DNS record and the certificate by itself. - 3Give your customers your domain and a plugin from the list below. They enter your domain and their own wallet. Your commission is added on your domain, so they cannot remove it.
| On your domain | What you get |
|---|---|
/v1/* | The same API. Your customers need no key: your file adds yours |
| Payment pages | Served under your domain, with no other name on them |
| Your commission | Paid on-chain to your wallet with each payment |
| Plugins | Download them below, rename them if you wish, and hand them to your customers |
| More levels | To let a customer resell under their own domain, make them a file with this same form: your domain as the API address, no key, their wallet and their commission. No depth limit; 20 wallets at most on one payment. A customer sees the total taken and their own share, not what the levels above take |
Need one key per customer?
The advanced relay lets you issue, price and suspend each customer separately. It needs the Cloudflare command line.
Downloads
Plugins and tools
Ready-made shop plugins with no brand on them: rename them and ship them as yours. The shop enters the payment address and its wallet.
- WooCommerceWordPress shopsDownload .zip
- WHMCSHosting billingDownload .zip
- PrestaShopOnline shopsDownload .zip
- OpenCart 4Online shopsDownload .zip
- Easy Digital DownloadsDigital productsDownload .zip
- FOSSBillingHosting billingDownload .zip
- PaymenterHosting billingDownload .zip
- Documentation for AIEverything in one .md fileDownload .md
Before completing an order, every plugin reads the payment back and checks the wallet, the reference, the amount and the currency. A fake notification changes nothing.
Good to know
Test mode and rules
Test mode
- A
wl_test_…key works like a live one, with no real money. - Answers carry
"test": true. - The crypto page is not shown for test payments: try it with a small live payment.
POST /v1/payments/{id}/test-confirmmarks a test payment as paid.- Notifications are sent and signed exactly as in live mode.
Rules
- You are responsible for the merchants you bring, at every level below you.
- No illegal goods or services, no fraud, no payments taken without delivering.
- Tell your merchants what they are charged: the fees of every level are taken from each payment.
- Keep your key secret. If it leaks, write to us and we replace it. A key used against these rules is suspended.
FAQ
Questions
As soon as the payment is confirmed. It is split on-chain in one go: the merchant, every wallet in the split list and the platform are paid at the same moment. Nothing is held and there is nothing to withdraw.
Ready to start?
Write to [email protected] and receive your key.