From your website
to your wallet.

Use a payment link for a fixed-price product, or create invoices from your server for dynamic orders.

1. Simple HTML button

Add your public wallets, then create a product in Payment buttons. Copy the HTML generated there and paste it into your page.

<a href="https://YOUR-DOMAIN/Pay.aspx?product=PRODUCT_ID"
   target="_blank" rel="noopener">Pay with Crypto</a>

Product prices are stored on the server. Changing the HTML cannot change the payable amount. Public product links do not identify an authenticated customer or a merchant order; reconcile those orders manually in the dashboard.

2. Dynamic checkout from your server

Generate an API key in Developers. Store it in a server-side configuration secret. Create an invoice with a unique order reference and a native crypto amount.

POST /api.ashx?action=api-create
Authorization: Bearer dc_YOUR_SECRET_KEY
Content-Type: application/json

{
  "order": "ORDER-1001",
  "title": "Online course",
  "asset": "usdt-tron",
  "amount": "49.00"
}

The response includes Id, url, amount, Asset, Address, Status, and Expires. Store the invoice ID, amount, and asset on your server before redirecting the customer to url.

The exact payable amount includes a small matching adjustment. Do not recompute it in the browser. Reusing the same order reference and parameters returns the existing invoice, including an expired one. Use a new attempt reference for a replacement invoice.

3. Verify fulfillment on your server

GET /api.ashx?action=api-status&id=INVOICE_ID
Authorization: Bearer dc_YOUR_SECRET_KEY

Only fulfill when Status == "paid". Match OrderId, Asset, and amount against your stored invoice. Mark fulfillment atomically in your own database so repeated status checks cannot duplicate delivery. Poll no faster than once per minute per order, with backoff on HTTP 429/503.

This release does not send webhooks. The checkout asks customers to submit a transaction ID and verify it again after finality. Your server polls the stored verified result; status reads do not trigger blockchain scans.

Supported asset identifiers

135 additional Ethereum ERC-20 tokens

These tokens are accepted on Ethereum mainnet only. Matching symbols on other networks are not supported by this catalog. Ethereum RPC must support finalized blocks. Checkout verifies the contract decimals before creating a token invoice. Fiat invoices require a fresh CoinGecko rate for the exact contract.

Payment matching and expiry

An invoice is valid for 30 minutes. Its exact amount is reserved globally for the same asset and address for 25 hours. Network block time must fall within the invoice window. Verification can finish within 24 hours after expiry. Late, partial, overpaid, wrong-network, or wrong-token transfers are not marked paid. Ask the merchant to resolve them directly.

One transaction can settle only one invoice. Split payments, internal ETH transfers, batched transactions for multiple invoices, rebasing tokens, fee-on-transfer tokens, and automatic exchange are not supported.

Operations

Provider outages return an error; they never confirm a payment. Bitcoin uses the configured explorer provider. Ethereum uses your HTTPS mainnet JSON-RPC endpoint. TRON uses your configured mainnet SolidityNode provider and API key. The operator must validate the deployment before enabling live payments.

Open merchant workspace →