WooCommerce
Cards and crypto on any WordPress store.
Take card and crypto payments on your own site. Create a free account, add your payout wallet and an API key — then cards and crypto each take one call, every payment shows in your dashboard, and the money settles straight to your own wallet.
For AI assistantsIntegrating with Claude, ChatGPT or Cursor? Give it this file.norpo-for-ai.md · the whole API, rules and copy-paste code in one page.Download fileBase URL https://api.norpo.io. JSON over HTTPS, no SDK, no sandbox: the requests on this page are the live ones. Money settles straight to your own wallet — Norpo does not hold it, except for the options you ask for: Telegram and crypto to balance, which credit your Norpo balance.
Pick one route. Each group below is complete on its own.
POST /v1/paymentsCryptoA named coin on a named chainSame API key. Each order gets its own deposit address; you receive the coin.POST /v1/ordersCrypto to balanceAny coin, 0.4%, withdrawn as USDTSwitch it on for your account. Your integration stays the same; crypto paid at checkout lands on your Norpo balance.No code changesNo code at all? Use a plugin, or send a payment link from your dashboard.
The key says who you are, so every payment lands in your dashboard — orders, volume, reports — and your server can get signed webhooks with retries. Money still settles straight to your own wallet.
One header on every request. Keys start with nrp_live_sk_, never expire and stop working the moment you revoke them. Keep the key on your server — never in browser, app or plugin code.
Authorization: Bearer nrp_live_sk_…
Build and test the whole integration without money. Create a test key in Settings → API keys → New test key; it starts with nrp_test_sk_. Payments made with it never reach a provider: order.url opens a Norpo test page (api.norpo.io/test-checkout/…) with two buttons, every answer carries"test": true, and so does the data of your webhooks. Test and live payments never mix — each key sees only its own.
curl -X POST https://api.norpo.io/v1/payments/cmud5…/simulate \-H "Authorization: Bearer nrp_test_sk_…" \-H "Content-Type: application/json" \-d '{ "outcome": "paid" }'# outcome: "paid" → payment.settled, "failed" → payment.failed# switch to a live key when you go live — nothing else changes
Send the amount; the wallet comes from your account. Send the customer to order.url, then read the status back or wait for the webhook. There is no minimum amount of our own.
One call for card and crypto. The payout wallet comes from your account, so it is never in the request; the key in the header is what identifies you.
curl -X POST https://api.norpo.io/v1/payments \-H "Authorization: Bearer nrp_live_sk_…" \-H "Content-Type: application/json" \-d '{"amount": 49.00,"currency": "USD","reference": "order-1042","callbackUrl": "https://shop.tld/hook","callbackFormat": "json","redirectUrl": "https://shop.tld/thanks"}'# → 201{"paymentId": "cmud5…","reference": "order-1042","status": "pending","order": {"kind": "onramp","url": "https://api.norpo.io/return/p/cmud5…","checkoutUrl": "https://pay.norpo.io/c/7PtToMTHohgeZH43skGLwk","settleAsset": "USDC"},"callbackFormat": "json","callbackSecret": "cbsec_8Kq2…"}# Send the customer to order.url — a Norpo waiting page that# opens the checkout, confirms the payment and, with# redirectUrl, returns the customer to your site.# Every payment made this way appears in your# dashboard: orders, volume, reports and webhooks.
| Field | What it does |
amount | Required. The price, e.g. 49.00 — not cents. |
currency | Three-letter code, default USD. Bill in the customer’s own currency: local methods only appear for local money. |
reference | Your order id. Echoed in responses, the callback and webhooks — match payments by it. |
redirectUrl | Where the customer goes after paying. The waiting page sends them there once the payment is confirmed; without it the page just says the payment arrived. |
callbackUrl | Optional. Norpo tells this URL when the payment settles — see Confirm it. |
callbackFormat | Send "json": the callback becomes a signed JSON POST, and the response carries a callbackSecret for this payment. Store it with the order to verify Norpo-Signature. |
customerEmail | Optional. Pre-fills the checkout and goes into your records. |
The waiting page. order.url is always a Norpo page, not the checkout itself. It opens the checkout in a new tab, keeps the customer’s place, shows the payment once it lands and, when you set a redirectUrl, sends the customer back to you. Card checkouts never return anyone on their own, so this is what brings them back. The raw checkout link is in order.checkoutUrl if you need it.
Two ways to hear about a payment: webhooks for the whole account (below), or a callbackUrl on the payment itself — handy for plugins and bots. Create the payment with "callbackFormat": "json" and Norpo POSTs a signed JSON event to that URL. Check Norpo-Signature with the callbackSecret from the create response: an HMAC-SHA256 of {t}.{body}, the same scheme as webhooks. Make the handler idempotent — the same event can arrive twice.
Norpo-Event: payment.paidNorpo-Signature: t=1790497260000,v1=5f2c…{"id": "evt_1ae3…","event": "payment.paid","created": 1790497260,"data": {"id": "cmud5…","status": "paid","reference": "order-1042","amount": 49,"currency": "USD"}}# verify the signature, match by id or reference, then fulfil
Every answer POST /v1/payments can give, and what to do about it.
| When | What to do | |
| 201 | Payment created | Send the customer to order.url. Keep paymentId; poll it or wait for the webhook. |
| 400 | The body is malformed — no amount, not a number, broken JSON | Read issues: each entry names the field and what is wrong with it. |
| 401 | Missing API key — no Authorization header | Send Authorization: Bearer nrp_live_sk_… on every request. |
| 401 | Invalid API key — wrong or revoked key | Create a new key in Settings → API keys. A revoked key never comes back. |
| 403 | account_not_active — the account is suspended | Contact support. |
| 422 | No payout wallet on the account | Add an EVM payout wallet (0x…) in Settings, then retry the same request. |
| 422 | The payment network rejected your payout wallet | Use an EVM address (0x…) from a wallet you control — not an exchange deposit address, a contract or a burn address. |
| 422 | Amount is below the minimum for the method you forced with kind or method | Raise the amount, or leave kind and method out and let Norpo pick. |
| 429 | Too many requests | Back off and retry. |
| 502 | The payment network did not answer | Not your request. Retry in a minute; if it keeps failing, contact support. |
| 503 | No payment method available for this request | Usually a kind or method that is not on for your account. Leave them out, or ask support. |
Add an endpoint in the dashboard under Webhooks. Norpo POSTs JSON to it when a payment settles and retries for about ten hours until you answer 2xx. Check the Norpo-Signature header before trusting the body: it is an HMAC-SHA256 of {t}.{body} with your endpoint secret.
Norpo-Event: payment.settledNorpo-Signature: t=1790497260000,v1=5f2c…{"id": "evt_9a41…","event": "payment.settled","created": 1790497260,"data": {"paymentId": "cmud5…","reference": "order-1042","amount": 49,"currency": "USD"}}# match by paymentId or reference; answer 2xx fast;# the same event can arrive more than once — use "id"
Card and crypto payments settle to your own wallet, which Norpo cannot spend from, so a refund is paid from your Norpo balance in USDT (TRC-20): minimum $5, network fee $1. Name the payment and refunds against it can never exceed what was paid. Your webhooks receive refund.created; the status turns paid with a TRON transaction hash once it is sent.
curl -X POST https://api.norpo.io/v1/payouts/refunds \-H "Authorization: Bearer nrp_live_sk_…" \-H "Content-Type: application/json" \-d '{"paymentId": "cmud5…","address": "T…customer","amount": 15,"reason": "Damaged item"}'
Let an AI agent bill your customers. Norpo runs a Model Context Protocol server: point any MCP client at it with your API key and the agent can create payments, check their status and read your balance. It cannot withdraw or send money.
URL: https://api.norpo.io/mcpHeader: Authorization: Bearer nrp_live_sk_…# toolscreate_payment amount, currency, reference → paymentId, order.urlget_payment paymentId → statuslist_payments recent paymentsget_balance balance in USD, read-only
For example, in Claude Code: claude mcp add --transport http norpo https://api.norpo.io/mcp --header "Authorization: Bearer nrp_live_sk_…". Use a separate key for the agent so you can revoke it on its own.
Every card payment opens the same checkout. Nothing to integrate: the buyer picks how to pay there, and your webhook or callback fires the same way whichever they choose.
Exchanges often take their withdrawal fee out of the amount sent. When what arrives is short by no more than 3% of the order — and never more than $1 — the order still closes as paid. A bigger gap keeps the order open: the checkout tells the buyer how much is missing and they send the rest to the same address. Your callback fires once, when the order is complete.
These options are off until they are switched on for your account. Crypto to balance and Telegram · CryptoBot you switch on yourself; for Changelly, ask in Telegram:
If you only need crypto, you can take crypto only. Cards, PayPal and local methods are switched off for your store, and the checkout opens straight on the crypto page: the buyer picks a coin and network and pays from an exchange or a wallet. The fee is 1.5% with the money straight to your wallet, or 0.4% with crypto to balance. Switch it on yourself in Settings → What buyers can pay with, or ask us in Telegram. Your integration stays the same, and you can switch back to all methods at any time.
A cheaper way to take crypto. Buyers pay in any coin at checkout, you pay 0.4% instead of 1.5%, and the money collects on your Norpo balance in USD until you withdraw it as USDT (TRC-20). Cards are not affected, and you do not change any code.
| Standard crypto | Crypto to balance | |
| Your fee | 1.5% | 0.4% |
| Where the money goes | Straight to your USDC (Polygon) wallet | Your Norpo balance, in USD |
| How you get it | Automatic, with every payment | You withdraw as USDT (TRC-20) |
| Who holds it | You | Norpo, until you withdraw |
| Coins | The usual checkout coins | Dozens of coins and networks |
| Minimum order | Per coin | From $1 on Polygon to $50 on Ethereum, by coin and network |
| Availability | On by default | One click in the dashboard |
The difference that matters: with standard crypto the money reaches your wallet by itself. With crypto to balance Norpo holds it until you withdraw.
An order for $250, paid in any coin:
| Amount | What happens | |
| Order | $250.00 | The buyer pays this, plus the conversion cost if the coin is not USDT on TRON |
| Your fee | −$1.00 | 0.4% |
| On your balance | $249.00 | Stays there until you withdraw |
| Network fee | −$3.00 | Per withdrawal, not per payment |
| Reaches your wallet | $246.00 | As USDT (TRC-20), within 60 minutes to 24 hours |
The buyer pays the order price plus a conversion cost, unless they pay in USDT on TRON. It is included in the amount they see, and you do not pay it. You are credited the order amount minus 0.4%, whichever coin was used, so a coin’s price moving later does not change your balance.
If you use the checkout, a payment link or a plugin, there is nothing to do. The buyer sees more coins, and your webhook payment.settled fires as before.
If you show crypto on your own page with POST /v1/payments/:id/crypto, the coins go to your balance too. Show amountText, because it keeps every digit of the amount. The amount holds for validMinutes; after that, request the same coin again.
POST /v1/orders does not change: those orders still go straight to your wallet at the usual rate.
Accept a named coin on a named chain, with the same API key. Each order gets its own deposit address and settlement forwards to your account’s payout wallet — or, for coins on other networks, to the wallet you pass for that network.
ticker) and the amount.payTo and the amount, ideally as a QR code.Accept a named coin on a named chain. Each order opens its own deposit address — never reuse one. Coins on Polygon, BNB Chain and Ethereum settle to your account’s payout wallet; for other networks pass "wallet" on that network.
curl -X POST https://api.norpo.io/v1/orders \-H "Authorization: Bearer nrp_live_sk_…" \-H "Content-Type: application/json" \-d '{"ticker": "polygon/usdc","amount": 25,"callbackUrl": "https://shop.tld/hook","callbackFormat": "json","reference": "order-1042"}'# → 201{"id": "cmsey…","status": "pending","ticker": "polygon/usdc","amount": 25,"payTo": "0x2FE2…9580","callbackSecret": "cbsec_8Kq2…"}# tickers: btc · eth · xmr · sol/sol · trx · ltc# polygon/usdc · erc20/usdt · trc20/usdt …
With "callbackFormat": "json" the callback is a signed POST, verified exactly like card payments with the order’s callbackSecret. It arrives after the deposit confirms on-chain.
Norpo-Event: order.paidNorpo-Signature: t=1790497260000,v1=9d07…{"id": "evt_77c0…","event": "order.paid","created": 1790497260,"data": {"id": "cmsey…","status": "paid","reference": "order-1042","amount": 25,"coin": "polygon/usdc","amountReceived": "25.000000","txHash": "0x4b…9af"}}
Integrated before October 2026? Nothing to change: payments and orders created without callbackFormat keep receiving the original GET callback, and every field you read today is still returned. Switch an integration over whenever it suits you by adding "callbackFormat": "json" to new orders.
Failures come back as JSON. For a bad or missing field (400) message is just "Invalid request" — the reason is in issues, one entry per field. Other errors put the reason in message.
| Meaning | What to do | |
| 201 | Done — the order exists | Use the returned id; it is the only handle you get. |
| 400 | A field is missing, malformed, or the provider refused | For a field, read issues — it names the field and what is wrong. Where the provider refuses, its own sentence comes back in message unchanged. |
| 404 | No such order | Check the id. Ids are returned once, at creation. |
| 422 | Valid request, cannot be fulfilled | Usually no payout wallet on the account, or the network rejected that wallet. The message names the cause. |
| 429 | Rate limited | Back off and retry. The limiter is per IP. |
| 502 | Upstream unreachable | Not your request. Retry shortly; if it persists, tell us. |
polygon/usdc order takes USDC on Polygon. The same coin on another chain is a different asset and the funds are lost. The API checks the shape of your receiving address, not which chain you meant.For a store, billing panel, forum or bot you already run. Free; connect each with your Norpo API key and it settles to the payout wallet in your account.
Cards and crypto on any WordPress store.

Every unpaid invoice gets a card-and-crypto pay button.
Paid user upgrades and Resource Manager sales.
Open-source billing for hosting companies and VPN providers.

Gateway extension for Paymenter v1, the open-source billing panel for game and VPS hosts.
Sell software, ebooks and license keys on WordPress with cards and crypto.

Membership sites on WordPress: one-off and fixed-term levels paid by card or crypto.

Payment extension for OpenCart 4 stores.
Payment module for PrestaShop 1.7.6, 8 and 9.
Payment method for Magento 2.4 and Adobe Commerce.
Take payments inside a bot you already run. Python and Node.
The things that actually trip people up, in the order they hit them.
nrp_live_sk_… in a browser, an app or a plugin someone else can read. If it leaks, revoke it in Settings → API keys — it stops working at once.250.00, not cents. Currency is the three-letter code; the customer pays in it and you are paid out in crypto — ETH, USDC or USDT (Polygon or BEP-20), or POL.Something not covered here? Ask on @norpoio — a real person answers.