A non-custodial payment gateway that routes the world's payment methods through your own accounts. Stripe, PayPal, bKash, Razorpay, MoMo, bank transfers in Bangladesh, Pakistan and India, Bangla QR, plus USDT/USDC on BSC and TRON — 159 rails across 9 regions. Money flows merchant ↔ gateway ↔ merchant. We never touch funds.
Most shops still confirm bKash, Nagad and bank payments the slow way: open the app, scroll the SMS, match it to an order. It works at ten orders a day. It quietly breaks at a hundred.
Someone has to open the wallet app, find the SMS and match it — while the buyer stares at a pending screen.
Two Tk 1,500 payments a minute apart. Which order was which? By hand, it is a guess.
An edited screenshot looks exactly like a real payment until you check the account — and by then the order shipped.
Orders placed at 2 a.m. wait until morning. Many of those buyers do not wait.
Four steps. You own the first one; we do the rest.
One API call, or the module you already installed. You send an amount and your own order number — nothing else.
The same hosted page offers every rail you've switched on — stablecoins, Binance Pay, mobile wallets or cards. You don't build a screen per method.
On-chain scanners and wallet feeds run every minute. The payment is matched to the exact invoice by amount and reference — no screenshots, no manual approval.
A signed webhook fires the moment the money is confirmed, with a delivery log and automatic retries. Your order flips to paid on its own.
Not a script you host and patch — a service that watches every rail for you, day and night.
Mobile wallets, 115 banks, Bangla QR, stablecoins and global cards. Turn them on in your dashboard — they appear at checkout.
The free ClaudePay Merchant app reads your bKash, Nagad and Rocket SMS and confirms the order the moment the money lands.
Every payment event, HMAC-signed, logged and retried until your site says OK.
Paid, pending and expired in real time, by website, method and day.
Send a link on WhatsApp or email. It flips to Paid by itself.
Your bKash, your bank, your wallet. We route and verify — the money never stops with us.
The money goes buyer → you. Claude Pay never holds it.
Two-factor sign-in, signed notifications and a full audit trail of every action.
Wallets, cards, bank transfers, Bangla QR and stablecoins — pick a market to see what your buyers there can pay with.
70 methods · paid in BDT
Wallets, banks, QR, stablecoins and cards all come in through one checkout. Out goes the money to your own account, a signed webhook to your site and an alert to your phone.
Shopify is not built yet — ask for it and it moves up the list.
Ready-made modules for Dhru and GSMTheme, free plugins for 8 store platforms, and a REST API for everything else.
Battle-tested in production hosting / GSM-unlock shops. Drop the module in, paste a Bearer key, customers pay in USDT and balances top up automatically.
One-tap installer for any GSMTheme site. Upload two PHP files, visit the installer URL once, paste your API key — customers can pay via every rail on your ClaudePay account and invoices flip Paid automatically.
One endpoint to create an intent, one signed webhook on payment. Idempotency keys, custom IDs, multi-method checkout sessions — everything documented.
Classic and block checkout, HPOS. Install the plugin, paste your API key — orders flip to paid on their own.
Download & setupNative gateway for WHMCS 8. Any invoice currency; part payments and double payments land as credit, never lost.
Download & setupPrestaShop 1.7.8, 8 and 9. Orders wait as “Awaiting Claude Pay payment” and move to Payment accepted when it confirms.
Download & setupOpenCart 4. You pick the waiting and paid statuses; an order you already shipped is never touched again.
Download & setupMagento 2.4 / Adobe Commerce. Paid orders get an invoice and move to Processing.
Download & setupPay button on every invoice; the payment is added to the invoice as soon as it confirms.
Download & setupFor hosts selling ISPmanager, VPS and dedicated servers through BILLmanager 6.
Download & setupNot built yet. Tell us if you need it — we'll get back to you with a realistic timeline.
Don't see your platform? Tell us what you need — most clean-REST integrations ship within 1–2 weeks.
Same wallets, same bank accounts, same money. Minus the checking.
Whatever you sell, ClaudePay routes the payment to the rail your customer prefers and the account YOU control on the other end.
Drop the Dhru Fusion module in, point it at your ClaudePay key. Plans renew automatically; balance tops up the moment the on-chain TX confirms.
Learn moreMonthly or yearly billing cycles handled at the API. Webhook fires on renewal; failed charges retry on a signed delivery log.
Learn moreFree plugins for WooCommerce, PrestaShop, OpenCart, Magento and Drupal, or the hosted checkout via the REST API. Customer picks crypto or local fiat — money lands directly in your account on each rail.
Learn moreOne intent per seller, each routed to the seller's own gateway credentials. We never custody anything — payouts are the original payment, no settlement step.
Learn moreUSDT / USDC on BEP-20, TRC-20, ERC-20, plus Binance Pay for customers without a wallet. Deposits confirm within seconds — your app is notified instantly.
Learn moreIf you can call a REST endpoint and receive a signed webhook, you can use ClaudePay. Build the flow that fits your business — we'll add adapters on request.
Learn moreRun separate shops from a single Claude Pay account. Each website keeps its own name and logo on the payment page, its own orders in your reports, and its own webhook — so one shop never hears about another's customers.
Custom PHP, Laravel, WordPress, or anything else — you don't need a ready-made plugin. Tell us about your site and we'll help you add ClaudePay and start accepting payments.
Free · we'll reach out to help you set it up
One Bearer token, ability-scoped per key. Idempotent intent creation. Signed webhook delivery with retries. And ready-made modules for Dhru Fusion, WooCommerce, WHMCS and more if that's your stack.
$ch = curl_init("https://claude-pay.com/api/v1/payment-intents");
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
"Authorization: Bearer cp_…",
"Content-Type: application/json",
],
CURLOPT_POSTFIELDS => json_encode([
"method" => "bep20",
"asset" => "USDT",
"amount" => 25.00,
"custom_id" => "ORDER-1042",
]),
]);
$intent = json_decode(curl_exec($ch), true)["data"];
// $intent["receive_address"], $intent["expires_at"]On the direct rails there is no processor in the middle holding your funds — payments arrive in wallets and accounts you already own.
Scanners match the exact amount to the exact invoice. No screenshots, no approving payments one by one.
Add a method in your dashboard and it appears at checkout. Your code doesn't change.
We don't take a cut of your payments — the plan is a flat monthly fee. The saving comes from letting buyers pay in stablecoins, where the cost is network fees rather than a percentage. Change any number to your own.
≈ 500 orders a month
Defaults are a common card-processing rate. Put in whatever you actually pay — the figures below use your numbers, not ours.
An estimate, not a quote. Card rates vary by country, card type and your own contract; network fees vary with chain congestion. Claude Pay never takes a percentage — you keep paying each gateway directly, which is why your own rate is the one that matters here.
Subscriptions go to our treasury — through the same flow your customers use to pay you.
Loading plans…
Need a full comparison? See full pricing →
TOTP 2FA enforced for admins and live merchants
Argon2id password hashing
Webhook payloads signed with HMAC-SHA256 + timestamp
Audit trail for every admin and merchant action
Unique-amount option to prevent invoice collisions
Server-to-server calls authenticated with rotating credentials
Straight to YOUR account — your Stripe balance, your PayPal, your bKash, your wallet. Claude Pay holds nothing. The merchant brings the gateway credentials; we just orchestrate the checkout.
Aggregating (the Stripe/PayPal model) requires us to hold a payment-aggregator licence in every country, do KYB on every merchant, and become a counterparty for chargebacks. BYO means you're the merchant of record on each gateway — fewer middlemen, lower fees, faster payouts.
Two options per merchant — block simultaneous same-amount invoices, or make each invoice amount unique automatically. Your customer sees exactly what they expect either way; collisions are impossible.
Yes. Dhru Fusion and GSMTheme have ready-made modules, and there are free plugins for WooCommerce, WHMCS, PrestaShop, OpenCart, Magento 2, HostBill, BILLmanager and Drupal Commerce (Setup → Store plugins). Anything else: our REST API with hosted checkout — one redirect, one webhook.
Use whichever your customers already trust in your country: Stripe for global cards, Razorpay/Paytm in India, bKash in Bangladesh, MoMo in Vietnam, Mercado Pago in LATAM, USDT/USDC for the crypto-native crowd. You can offer multiple on the same invoice.
Fiat: 1–5 seconds after the customer pays. Crypto: 30–90 seconds depending on the chain. Binance C2C: as soon as the transfer settles.
Connect your wallets and banks in minutes. Every payment after that confirms itself.