Best Crypto Payment APIs for Developers

Which crypto payment APIs should you shortlist?

Shortlist CoinGate or BitPay for managed collection if your business qualifies, and BTCPay if getting paid directly and controlling the setup is worth the work. The other options below fit particular needs, but each has real open questions. Your developer can estimate the work of running the order journey; the agreement, the business approval and how the money reaches you decide whether the proposal is worth buying.

An API lets you put payment handling inside your own business system, but the work after checkout remains. Someone must decide when an order ships, recognise a repeated message, handle a late payment and keep a return from falling between support and the bookkeeping.

The cards keep their positions from the overall gateway ranking, which weights cost 25%, fiat 15%, licences 15%, coins 10%, integrations 10%, features 10%, support 10% and onboarding 5%. The integrations score counts plugins, APIs and sandboxes and says nothing about code quality, notification delivery, speed, security, development hours or API uptime. The ranking methodology explains the formula.

Every headline here assumes your business, owners, activity and customers get approved, with the coins and networks you need switched on. The products compared are BitPay Acceptance (under its Inc. or B.V. agreement), UAB Decentralized's CoinGate Standard, B2BINPAY Merchant (El Salvador or Mauritius, depending on the agreement), OxaPay's ordinary Invoice, Plisio's BTC API and self-operated BTCPay software. It's still unclear which company you'd contract with at B2BINPAY, and who OxaPay's and Plisio's current counterparties are and what permissions they hold. BTCPay users also need approval from any host or partner they use.

The prices on the cards are ordinary incoming fees only: BitPay's entry band, CoinGate Standard, OxaPay's ordinary invoice, Plisio BTC, B2BINPAY's coin percentage (before its per-payment minimums and tier changes) and BTCPay's software charge (before running costs). They leave out minimum fees, network charges, conversion margins, bank and partner costs, and application, monthly, refund and exit costs, plus any custom or high-risk pricing. A cost nobody has priced isn't zero.

1. 1

   CoinGate

   Standard for an eligible shop wanting hosted checkout and useful payment records

   81/100

   1%
   • Order references connect shop purchases to payment and credited amounts.
   • Retries and replay are described in its docs and can help a developer investigate missed updates.
   • Later shortfalls or refund changes may need a fresh lookup, and country approval, the quote margin and account rules still apply.
   Read review ↗Visit site
2. 3

   BitPay

   Acceptance for an approved US or Canadian merchant wanting managed collection

   73/100

   2% + $0.25
   • Its testing guidance covers awkward orders as well as successful payments.
   • Full and partial sale returns have defined stages.
   • New EEA, UK and Australian onboarding is paused. The fixed per-order charge, the application fee and the return rules that differ by BitPay entity also need a look.
   Read review ↗Visit site
3. 9

   B2BinPay

   Business Merchant for an approved company with a defined deposit workflow

   62/100

   0.4%
   • Deposit states tell an ordinary payment apart from exceptions that need attention.
   • Transfer confirmation and deposit changes each have their own notification in the docs.
   • Its pages conflict on US service and restrict Canada, so you need a country decision. The contracting company, payment minimums and ordinary refund terms are still open.
   Read review ↗Visit site
4. 12

   BTCPay Server

   Self-operated software for a business able to own its payment operations

   57/100

   0%
   • Receiving Bitcoin into an external wallet can keep spending keys away from the payment server.
   • The refund workflow has approval and chain completion as different stages.
   • Hosting, upkeep and support need an owner, a host or shared Lightning setup changes who controls the funds, and we couldn't confirm detailed API guarantees.
   Read review ↗Visit site
5. 16

   Plisio

   BTC invoice API for a business weighing hosted collection

   49/100

   0.5%
   • Unique store references and returning an existing invoice are both described in the docs.
   • Related invoices can be linked when the customer changes payment currency.
   • A completion setting can accept a short payment. The current operator, ordinary returns, bank availability and maintenance commitments are still open.
   Read review ↗Visit site
6. 17

   OxaPay

   Ordinary Invoice for an approved business that wants to take crypto

   48/100

   1.5%
   • Invoice notifications tell an attempted payment apart from a paid one.
   • Manual acceptance, short payment and return states each get their own description.
   • Who the current counterparty is and what permissions it holds are unclear. Registration-country exclusions, inconsistent examples and the full refund cost also need answers.
   Read review ↗Visit site

Which option fits the way your shop works?

Choose the product that fits how you want to be paid and the work your team can reliably cover. A developer's preferred library won't help if you need a different coin or your business can't open the account.

Managed checkout for an ordinary business

CoinGate Standard is a good starting point for an eligible business that wants hosted checkout with an agreed receiving currency. Its order documentation lets you choose the coin the customer pays with independently of what you receive.^[7] That helps when customers prefer crypto but you want one balance to reconcile. The drawback is that you depend on the managed account and its quote.

BitPay Acceptance deserves a look for an approved US or Canadian merchant. Its country help pauses new EEA, UK and Australian onboarding and notes further product and US state limits.^[3] We'd settle availability before investing in development. A listed euro receiving currency or a licence elsewhere doesn't reopen a paused application.

A business with more involved deposit handling

B2BINPAY Merchant can suit a company willing to agree its wallet, deposit and receiving setup in detail. Its documentation gives late and excess payments a status called "Unresolved", which needs action from you, and treats a transfer confirmation and a deposit-status change as different events.^[15] That helps frame a bookkeeping workflow, though it leaves open whether each deposit is ready to withdraw and whether returns are automated.

Hosted crypto receipt with open commercial questions

OxaPay's ordinary Invoice product is an option only if its business and country rules fit you. Its useful feature is a distinct status for waiting, paying, paid, manual acceptance and a return in progress.^[19] Before choosing it we'd want to know the signing company, its permissions, who controls the funds and how returns work, and marketing about light paperwork leaves all of that open.

Plisio's BTC invoice API is worth a look if its account and hosted-wallet setup suit you. Its invoice reference describes a unique store reference and returning an existing invoice, with specific limits, and stops short of promising that every repeated action is harmless. Who the current counterparty is, and what maintenance it commits to, are still big gaps for a buyer.

Direct receipt with an operating team

BTCPay Server is a different kind of purchase: you run payment software instead of buying a managed account. Its general FAQ describes receiving Bitcoin directly without handing over spending keys.^[26] That's useful control for a capable team, and it gives someone the job of keeping the service current and available.

We couldn't confirm the detailed Greenfield API reference, so we don't know what retry protection, rate limits, authorisation or refund endpoints it offers. Put that gap into the estimate, along with the host and maintenance agreement.

When should your system release an order?

Release it only when the current payment record, the amount received and the agreed completion rule all match that order. A customer's browser coming back to your shop, or a message arriving at your server, is only part of the picture.

A webhook, or payment notification, can wake the shop's order system. A confirmation describes a network event. Neither word has one universal meaning for fulfilment, account credit and bank availability.

Our 15 October reading of BitPay's notification guide says its invoice notifications are unsigned and that you should check the current invoice, and that paid isn't a final, guaranteed state. We haven't looked at the reference again since.^[39] So don't ship orders just because a message arrived.

CoinGate's status reference treats confirming, paid and credited as different states, and its new and selected-payment windows expire at different stages.^[9] A late payment needs a real decision about the order and the money; changing a label in the shop doesn't undo a transfer.

Plisio shows why the amount matters. Its underpayment help lets a configured tolerance complete an invoice despite a short receipt, so the invoice reference's general fully-paid description has to be read with that setting.^[24] Your accounts should record what was received and any accepted shortfall, not the missing sale value.

Downloads need extra care: once a customer has the file or access, a mistaken release is hard to reverse, so settle how manual acceptance, a mismatched currency, expiry or a compliance review is handled before automating delivery.

What stops a repeated notification shipping an order twice?

Your shop needs one shipping decision for each order, even when messages repeat. Checking that a notification is genuine and preventing a duplicate shipment are different jobs.

CoinGate describes retries, stopping after failed attempts, manual replay and callback logs. Those help you investigate a missing update, while acting exactly once is up to your shop.^[5] Its payment callback also says later shortfall, excess and refundability changes don't generate another notification, so current order information matters for the books as well as for shipping.^[4]

A duplicate-safe request, sometimes called idempotency, solves a different problem: did the first request succeed when the screen timed out? It has to cover the action you're protecting. An order reference, a repeated message and a provider's retry key aren't interchangeable protections.

OxaPay's webhook document describes authenticity checks and limited attempts, but its acknowledgement wording and code examples differ, and so do the payment and invoice branches. OxaPay and your developer should clarify the intended handling rather than copy a sample blindly.^[18] We haven't shown a vulnerability or judged the API's security from those differences.

What do the headline fees come to?

Order size matters as much as monthly sales when a price includes a fixed amount per order. The example below shows how much.

BitPay's entry band is 2% plus USD 0.25 per paid invoice, from our 11 October reading; we couldn't recheck its page this time.^[37] CoinGate Standard lists a 1% fee, OxaPay ordinary invoices 1.5%, and Plisio's detailed BTC API row 0.5%. Those rates apply to the ordinary products only, not to branded, static, token or wallet products.^[23]

The calculator covers ordinary incoming accounts at BitPay Acceptance, CoinGate Standard (UAB Decentralized), OxaPay Invoice and Plisio BTC API, assuming each one approves you. You'd still need to know which BitPay agreement you'd sign (Inc. or B.V.) and who OxaPay's and Plisio's counterparties are. Amounts are in USD as a reference unit, not an exchange rate or a promised bank receipt.

It counts only those named rates, so the costs left out of the shortlist prices are left out here too. Lowest, difference and highlight labels compare these portions only, and annual values assume twelve identical months. The tool doesn't replay payment sequence across bands or work out released funds, profit, full savings or bank net.

CoinGate's Commercial Policy adds a risk margin to payment-processing quotes and doesn't price it. Automatic checkout conversion sits outside its own manual-exchange charge, but the quote margin still applies.^[12] OxaPay's pricing page prices white-label, static-address and Receive services apart from ordinary invoices, so a low headline rate may not cover the product you'd pick.

Is Coinbase Business Checkout worth a look?

Yes, for a qualifying Business account: the published repeat-request and completion features are good reasons to look at it. Talk to Coinbase about it on its own, because the Checkout overview publishes no new-account pricing.^[33]

The Coinbase Business review explains the old site address and how this product differs from the earlier one. Its availability help names only US and Singapore C corporations and LLCs, whatever the broader marketing says about account types, and activation needs business and owner verification. The agreement for your own jurisdiction and approval of your activity still apply.^[34]

Coinbase Business describes an optional retry key for creating a checkout and another for requesting a refund. That's useful when an uncertain response might tempt your system to create the action again. We couldn't find how long the key is kept, and it protects only those two requests, not every operation.^[31][32]

The Get and Create Checkout schemas list Base, although the wider payment marketing mentions more assets. Get Checkout says the success redirect shows only authorisation, not completed payment, and its refunded-amount field can appear once a refund is initiated.^[30] You need to know which asset and network are really enabled and what the final states are. Don't read a sample fee as a tariff, a large schema maximum as your capacity, or a fiat-denominated field as money in your bank.

What limits, testing and upkeep should your developer price?

Your developer should price the busy hour, the awkward payment and ongoing maintenance. A demo of one easy sale covers none of them, and neither does published documentation.

CoinGate publishes a default 200 requests per minute and a second limit of 500 orders per hour per business, dashboard orders included. A bigger request allowance doesn't let you create more orders than that.^[6] Estimate from your expected checkout traffic, bookkeeping updates and exception handling.

B2BINPAY's overview announces v3 for June 2025 and an old-version shutdown after December 2025. That's a dated supplier notice we haven't watched play out. Its 15-per-minute limit applies to unauthenticated requests, not to the capacity you'd buy for production.^[14] Its authentication guide describes access that expires, and the example lifetime of 3,599 seconds is just a sample. Budget time for keeping access working.

BitPay warns that its test environment doesn't reproduce the production experience and can simulate a completed payment, so use it to plan exception coverage and look elsewhere for proof of live compatibility.^[1] CoinGate likewise says its sandbox uses different currency and platform references and that production needs verification.^[8]

Libraries, specifications and package listings help a developer estimate the work, though the version you choose may not be maintained, may not suit your shop, may never have been independently audited and may carry no response commitment. Your estimate should name who covers changes and who fixes the integration after the original developer leaves.

Can your company, owners and customers use the service?

Your company, owners and customers have to fit the product and agreement you'd sign before an API is worth buying. Our 16 October 2026 document review approves no company or activity, and KYB is only verification; being accepted for a particular product or receiving setup is a further step.

CoinGate's merchant-country list includes the UK, Canada and many EEA countries but not the US.^[11] Its General Terms name UAB Decentralized and open an account only after compliance checks and confirmation. Your customer markets and lawful activity still have to match, since a listed country isn't approval for every business model.

B2BINPAY's AML policy names its El Salvador company and, in the main text, restricts US and Canadian residents and companies. Its shorter footer instead describes US service limited by an exemption and leaves Canada out. That conflict is still open, as is which El Salvador or Mauritius product agreement would apply, so don't assume an exemption is available to you.^[16]

OxaPay's current terms restrict use to the submitted and approved business and exclude, among other jurisdictions, businesses registered in the US. They refer only to "the Company", so we couldn't tell who the current counterparty is. Account restrictions can block assets.^[21] Plisio's linked Terms still carry a March 2019 update, describe service wallets and limit use to approved purposes, so you'd need to confirm the current operator and what it permits.^[25]

Self-operated software has no central merchant application, but permission to use the software isn't a financial licence, business approval or permission from a host, conversion partner or bank you choose. The right advisers can look at your business and service; this is general information, not legal advice.

Who controls proceeds, returns and bookkeeping?

Find out who can approve a movement of money and who can hold it up, and have your books follow each stage. A payment can be received, credited to your merchant account, made available, sent on, confirmed on the chain and posted by your bank, and those are six different events.

Under BitPay's Terms (our 11 October reading), Acceptance is a payment-agency relationship, not the general crypto-custody product that the broad custody category in the comparison table might suggest. The Terms also carry an application charge with no price given and refund conditions that differ by BitPay entity.^[38] Your own agreement decides how much you can spend on stock and how much has to stay available for returns.

With BTCPay, signing from an external on-chain wallet is different from keeping keys in a hot wallet on the server. A third-party host controls the server and can affect future checkout instructions, and a shared Lightning setup can put receipts into the host's wallet.^[27] Its Lightning FAQ covers the shared-wallet and liquidity responsibilities. How directly you receive the money depends on the configuration you pick.

For returns, BitPay's stages run from preview through allocated and pending to successfully processed, and a pending return shouldn't be marked finished in your books.^[2] BTCPay's refund guide likewise moves from a customer claim to approval, sending and chain confirmation. Your own account terms need to cover how a return is funded and who pays, what happens to the fee on the original sale, how the exchange is handled, and the network, destination and expected receipt. OxaPay's refund labels and Plisio's invoice feature aren't a complete refund tariff for ordinary sales.

For each order, keep a short record of your order reference, the provider's reference, the asset and amount received, fees, the credit to your account, fulfilment and any return. A transaction hash helps where a chain transfer exists, but an internal account movement may have none, which is why the provider reference matters. Fields, logs and exports come with no guarantee of complete accounting sync or of how long records are kept. Whoever does your books should review a sample statement before you accept an integration estimate.

The table below is background on each product, not proof that its API fits your shop or is secure. Its historical licence, bank, custody, coin and plugin fields aren't your enabled coins or an approved account. Its prices are ordinary incoming fees only: B2BINPAY's coin percentage (before per-payment minimums and tier changes that only move forward) and BTCPay's software charge, which is zero before operating, host, network, liquidity and partner costs. The same omissions apply, the monthly cost row isn't a full cost, released balance or bank net, and the overall score approves no API account.

	BitPay	CoinGate	B2BinPay	OxaPay	Plisio	BTCPay Server
Score	73/100 · #3	81/100 · #1	62/100 · #9	48/100 · #17	49/100 · #16	57/100 · #12
Payment fee	2% + $0.25	1%	0.4%	1.5%	0.5%	0%
Cost on $10k/month	$225	$100	$40.00	$150	$50.00	$0.00
Pays out to bank	AUD, CAD, CHF, EUR, GBP, MXN, NZD, USD	EUR, GBP, USD	EUR, USD	No	Not stated	Not stated
Stablecoin networks	USDC: Ethereum, Polygon, Arbitrum, Optimism, Base, Solana · USDT: Ethereum, Polygon, Arbitrum, Optimism, Solana · PYUSD: Ethereum · GUSD: Ethereum · USDP: Ethereum · EURC: Ethereum · BUSD: Ethereum, Polygon	USDC: Ethereum, BNB Smart Chain, Solana, Polygon, Arbitrum, Base, Optimism · EURC: Ethereum	USDT: Not stated · USDC: Not stated	USDT: Ethereum, Tron, BSC, Solana, Polygon, TON · USDC: Ethereum, BSC, Solana, Polygon, Base · DAI: Not stated	USDT: ERC20, TRC20, BEP20, TON, Solana · USDC: ERC20, Base, BEP20, Solana · TUSD: Not stated · BUSD: BEP20	USDT: Liquid, TRC20 (plugin)
Coins	19	12	Not stated	18	Not stated	14
Custody	Custodial	Custodial	Custodial	Custodial or non-custodial	Custodial	Non-custodial
Merchant KYC	Required	Required	Required	Light	Light	None
Rolling reserve	Not stated	Not stated	Not stated	Not stated	Not stated	none
Licence	Money transmitter (NMLS ID) (1496848); Virtual Currency Business Activity licence (NYDFS)	Crypto-Asset Service Provider (MiCA), Bank of Lithuania; licence No. 2, authorization code LB002323 (LB002323); Payment institution, Bank of Lithuania (EMT operations); licence No. 60, authorization code LB002324 (LB002324)	Digital Asset Service Provider (PSAD), B2BINPAY EL SALVADOR S.A. DE C.V. (PSAD-0064); Bitcoin Service Provider (PSB), B2BINPAY EL SALVADOR S.A. DE C.V.	Not stated	Not stated	Not stated
Plugins	WooCommerce, Shopify, Magento 2, WHMCS, Wix, BigCommerce	WooCommerce, Wix, Magento 2, WHMCS, OpenCart, PrestaShop	WooCommerce	WooCommerce, WHMCS, ClientExec, Blesta, WISECP, PrestaShop	WooCommerce, Magento, PrestaShop, OpenCart, WHMCS, BigCommerce	WooCommerce, Shopify, PrestaShop, Magento, BigCommerce, Odoo
Legal entity country	United States	Lithuania	Not stated	Not stated	Not stated	Not stated
Founded	2011	2014	Not stated	Not stated	Not stated	Not stated

What should you agree before building or changing suppliers?

Before you commit to development, agree on the service, who runs it and how unfinished work gets handled. The processor selection guide covers the wider buying decision; your API proposal should fit your real collection and return jobs.

Start with which company signs, in which country, for which activity. Then pin down the asset and network the customer pays with, what you receive, and whether it goes to your own wallet or your bank. The fiat-settlement guide explains why a credit in your account isn't yet spendable bank money. Don't build around a receiving method nobody has confirmed.

Complete quotes at your expected order size and frequency are the fair comparison. Our fee calculator guide covers the basic arithmetic, but the supplier still has to price the real payment journey, exceptions and operating work. A self-operated option also costs staff time and hosting. BTCPay's deployment FAQ separates free software from hosting; the operating budget is still yours to work out.

1. 
   01

   Agree the service

   Whoever signs the contract settles the signing company, activity, countries, customer markets, enabled assets and networks, receiving setup, full price and exit terms.

2. 
   02

   Walk through the order journey

   Your developer explains payment state and amount, repeated requests and notifications, expiry, partial payments, returns and who maintains the connection.

3. 
   03

   Match records to outcomes

   Whoever does your books matches real receipts, fees, provider credits, onward transfers and completed returns, and doesn't close an item just because a request was acknowledged.

4. 
   04

   Keep open work in view

   Whoever handles customers keeps references, records and promises to customers to hand, with a clear way to escalate and cover for absences.

Changing suppliers leaves old orders unfinished and doesn't carry old permissions into a new account. Work out how open invoices, late receipts, returns, records, consents and continuing charges will be handled, and don't assume credentials, payment references or customer authorisations move with you. Someone should own the old obligations until they're resolved under the agreement that applies.

Published support hours, retry schedules, releases and public ratings aren't measured uptime, security or resolution guarantees. Your support agreement should say what it covers when checkout is quiet but a customer return is still unfinished. Other providers aren't in this selection, and we haven't shown that they fall short.

Crypto payment API FAQ