Native BTC with its own full node — we do not read the chain through anyone else's API. Per-customer addresses, fee estimation by target block, and payouts from a single treasury.
Crypto payments, confirmed on-chain.
We issue a dedicated deposit address for every one of your customers, watch the chain ourselves, and call your server back once the payment has three confirmations. One integration, one treasury, one ledger that reconciles.
The chains we settle on
Live networks are in production today, carrying real payments. Everything marked as planned is on the roadmap and not yet available — we would rather say so here than in a support ticket.
The workhorse for stablecoin volume: cents per transfer and confirmation in under a minute. Energy and bandwidth are handled on our side, so a customer's transfer never fails for want of gas.
One address per customer takes all three. Token accounts are opened by us in advance, so exchanges that refuse to send to an unopened account send without complaint.
EVM support is designed and scheduled. The same address-per-customer model, the same callback contract — no second integration on your side.
Ships alongside Ethereum: once the EVM layer is in production, adding a chain is configuration rather than new code.
If your customers pay in a chain we do not list, tell us which and what volume. UTXO chains close to Bitcoin are the quickest for us to add.
Four steps, and none of them are yours
Your side does two things: ask for an address, and answer our callback. Everything between those is ours.
You ask for an address
One call with your API key and your own customer id. You get back an address that belongs to that customer and stays theirs — ask again and the same address comes back.
Your customer pays
They send from wherever they like — an exchange, a wallet, another service. Nothing on your side has to be running at that moment.
We watch the chain
Our own nodes see the transaction, count confirmations and record the payment against that customer. Dust and spam transfers are filtered before they ever reach you.
We call you back
After three confirmations we POST the payment to your endpoint and expect a short confirmation in return. No answer means we keep retrying — a credited payment is never silently dropped.
Two endpoints is the whole contract
No SDK to install, no library to keep up to date. Form-encoded requests and plain fields, so it works from any stack — including the PHP that is already running your site.
Your customer id is the key
Pass your own identifier. We store it against the address, and it comes back on every callback — no mapping table to maintain.
Idempotent by design
Asking twice returns the same address. Our callbacks carry the transaction id, so a repeated delivery cannot credit a customer twice.
Retries with growing gaps
If your server is down, the callback waits and comes back later. Every attempt is logged with the response we got, and you can see it.
IP allowlisting both ways
Your key only works from the addresses you give us, and our callbacks arrive from a fixed address you can allowlist in turn.
# POST, form-encoded. Your key, your customer id, the coin.
curl https://api.crypto4pay.net/v1/address \
-d key=$CRYPTO4PAY_KEY \
-d id_account=48201 \
-d coin=USDT_TRC20
# →
{
"address": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t",
"id_account": "48201",
"coin": "USDT_TRC20",
"network": "tron"
}
# We POST to your endpoint after 3 confirmations.
# Answer with a body containing "ok" — that is the whole protocol.
<?php
$id = $_POST['id_account']; // your customer
$sum = $_POST['amount']; // credited amount
$coin = $_POST['coin']; // USDT_TRC20, BTC, …
$tx = $_POST['txId']; // on-chain id, unique
if (already_credited($tx)) { echo 'ok'; exit; }
credit_balance($id, $sum, $coin, $tx);
echo 'ok'; // no "ok" → we retry later
What runs behind the two endpoints
The part you never see is the part that decides whether the money adds up at the end of the month.
Double-entry ledger
Every movement is a balanced pair of entries the database itself refuses to accept if it does not balance. Balances are derived, never edited by hand.
Our own nodes
Bitcoin and Tron run on our hardware. We read the chain directly instead of trusting a third-party indexer that can lag, cache or quietly go away.
Automatic consolidation
Funds move from customer addresses to one treasury on their own, with gas paid centrally. Your payouts come from a single balance, not a hundred scattered ones.
Priced history that holds still
Rates and fees are recorded as of the moment of the transaction. Last month's report does not change because today's price did.
Payouts under two locks
Withdrawals need a separate payment password and a second confirmation out of band. Signing happens where the keys live, not in the web interface.
Full audit trail
Who did what and when, for every address issued and every coin sent. When money goes somewhere unexpected, that question gets answered in seconds.
Tell us what you need to accept
We onboard companies directly — no self-serve signup, no automated approval. Write what your customers pay in and roughly what volume, and you will get a straight answer about whether we are a fit.
- A test key and a test address before anything goes live
- Help wiring up the callback on your side, in your code
- Pricing quoted per network, in writing, before you commit
- No custody of your customers' funds beyond settlement