Crypto Payment Gateway Currencies 2026: The Real Count
We counted every crypto payment gateway's supported currencies against its own public API on 24 September 2026. The marketed number is the longest list.
Key Takeaways
- Every gateway keeps at least four currency lists, and the number on the homepage is whichever is longest. CoinGate publishes all four on one page — price in, pay with, settle in, pay out — and on 24 September 2026 they held 55, 11, 11 and 13 entries. No two are the same list.
- The gap between marketed and countable is largest at the top. NOWPayments advertises 300+ in its hero and 350+ four blocks below it; its public endpoint returned 224 tickers. BitPay advertises 100+; its own currencies file carries 21 distinct crypto tickers.
- A third of the inflation is one coin counted many times. NOWPayments lists USDT ten times and USDC nine; 38 of its 224 tickers are an asset already on the list, leaving 186 distinct. Nothing states the unit being counted.
- What you can be paid in is not what you can keep. BitPay documents 15 crypto and 8 fiat settlement currencies. On CoinGate you can take XRP, TRON, BNB and Polygon at checkout and settle in none of them, while Bitcoin Cash is settle-only and cannot be paid in at all.
- The small gateways are the accurate ones. OxaPay could market 31 coin-network pairs and shows 18 coins; Plisio says 15+ and lists 18. Understating is rare enough to be worth pricing in.
Table of Contents
- The headline number is the longest list they have
- What we counted, and how to repeat it
- Four lists, not one: CoinGate in full
- Counting the same coin ten times
- BitPay: a hundred to pay, fifteen to keep
- The accurate ones are the small ones
- The fiat list is the biggest and nobody mentions it
- What to ask before you integrate
- FAQ
The headline number is the longest list they have
Pick any crypto payment gateway and the first thing it tells you is a count. Three hundred coins. Three hundred and fifty. More than a hundred. The number is doing a lot of work in the sales pitch and almost none in your integration, because a crypto payment gateway's supported currencies are not one list but at least four, and the one in the headline is the one that constrains you least. We spent an afternoon on 24 September 2026 checking each company's marketing claim against its own public API — every figure below comes from the gateway's own endpoint or its own documentation on that date, and every endpoint we used is linked so you can re-run it.
The pattern held everywhere we looked, and it is not subtle. Here is the whole finding in one table.
Read the first and last rows together, because they are the argument. The gateway with the biggest claim publishes no settlement list at all without an account; the gateway with the smallest claim publishes all four of its lists on a public page. Breadth of acceptance is cheap to advertise and cheap to extend — a conversion step at checkout does most of it — which is exactly why it became the number everyone leads with.
What we counted, and how to repeat it
No account, no key, no scraping. Four of the six gateways answer an unauthenticated GET with their full currency table, which means any merchant can check a claim in about ninety seconds before signing anything. Two do not, and we say so rather than guessing at their numbers.
The four endpoints, all open:
- api.coingate.com/v2/currencies — the richest of the four. Every entry carries a
merchantobject with three booleans:price,payandreceive. - api.nowpayments.io/v1/currencies — a flat array of tickers. Add
?fixed_rate=trueand it drops from 224 to 212, which is a fifth list nobody advertises. - bitpay.com/currencies — 196 entries, fiat and crypto together; a
chainfield separates them. - api.oxapay.com/api/currencies — coins with a nested
networkList, so you can count coins and coin-network pairs separately and see the difference.
Plisio's /api/v1/currencies answers "Please check your secret key is correct and domain is verified" to an anonymous request, so we used the list printed on its homepage instead. Cryptomus exposes no public currency endpoint we could find, which leaves its "More than 100 cryptocurrencies supported" unverifiable from outside an account — not wrong, just uncheckable, and that distinction matters when you are choosing who to trust with a checkout. The same method we used on invoice-window volatility applies here: take the vendor's own endpoint over the vendor's own paragraph.
Four lists, not one: CoinGate in full
CoinGate does something none of its rivals do: it publishes four tabbed currency lists on one public page — Accepted by merchants, Settlements, Crypto Payouts & Withdrawals and Deposits. That single design decision is the best evidence in this piece that the lists are genuinely different things, because a company that thought they were interchangeable would print one.
We cross-checked the tabs against the API's merchant flags and they agree. Fourteen distinct crypto assets appear somewhere across CoinGate's documentation. Seven of them appear on all four lists.
Four asymmetries are worth naming, because each one is a decision somebody makes for you the first time it bites. XRP, TRON, BNB and Polygon are pay-only: a customer can settle an invoice in them and you cannot hold them, so the gateway converts on arrival whether you wanted that or not. Bitcoin Cash runs the other way — you may settle in it and deposit it, but no customer can pay you in it. SHIB and WBNB exist only on the outbound side, which makes sense once you notice that payouts and acceptance are different products with different risk teams behind them.
One inconsistency we will flag rather than adjudicate. The FAQ on the same CoinGate page says "You can accept payments in BTC, LTC, TRX, ETH, USDC, BCH, XRP, POL, DOGE, SOL, stablecoins and more" — naming BCH as acceptable — while the widget directly above it and the API both put Bitcoin Cash on the settlement and deposit tabs only. Prose drifts; endpoints get deployed. When the two disagree, we take the endpoint, and so should your integration.
Counting the same coin ten times
NOWPayments returned 224 tickers on 24 September 2026 against a marketed 300-plus, and the shortfall is only half the story. The other half is that the 224 is not 224 things. USDT on Tron and USDT on Ethereum are one asset to your customer and two rows in the list. Collapse the chain variants and 186 distinct assets remain — 38 of the entries are a repeat.
We are not calling this dishonest, because there is a real case for counting pairs: a merchant who accepts USDT on Tron and not on Ethereum genuinely supports something narrower than one who takes both, and the choice of chain changes what the payment costs your customer. The problem is that nothing on any of these pages states which unit is being counted, so you cannot compare two gateways' figures at all. Apply pair-counting to OxaPay and it markets 31; apply asset-counting to NOWPayments and it markets 186. Both numbers are defensible and neither is the one on the homepage.
Two smaller things fell out of the same request. NOWPayments' hero says 300+ and a panel a few blocks down the same homepage says 350+ crypto coins & 75+ fiat coins, which is a company disagreeing with itself above the fold. And ?fixed_rate=true cuts the list to 212 — meaning 12 assets cannot be used with the paid rate-lock option, a restriction we have not seen documented anywhere in the marketing.
BitPay: a hundred to pay, fifteen to keep
BitPay is the clearest illustration of the accept-versus-settle gap because it documents both sides properly. Its "over 100 cryptocurrencies" claim is still live and still quoted in 2026 roundups; it was published in April 2024. Meanwhile its settlement documentation names exactly what a merchant can be paid out in, and the list is short enough to print.
Notice that the two useful numbers, 15 and 8, are the two you have to go to the developer documentation to find, and the number in the press release is the one that reaches every comparison article. To be fair to BitPay, the 100-plus is not a fabrication — broad acceptance at checkout is typically delivered by converting an unusual coin into a supported one on the way in, so the customer really can pay in something exotic. It just does not tell you anything about your own balance sheet, which is what a merchant is actually asking when they ask how many coins are supported.
The accurate ones are the small ones
The inversion is consistent enough to be a rule of thumb: the smaller the gateway's list, the more accurately it is described. Plisio says "Accept 15+ Supported Coins" and then shows 18. OxaPay prints no headline count at all, shows 18 logos, and its API returns exactly those 18 — while carrying 31 coin-network pairs it could have counted instead.
There is a commercial reading of this that is not simply "small companies are more virtuous". A gateway with eighteen coins is selling reliability and a clean integration, and a precise number supports that pitch. A gateway with two hundred is selling reach, and reach is measured in impressions rather than in what settles. Both are coherent strategies; only one of them survives contact with your accountant. Monero's presence on OxaPay is worth a separate note for anyone accepting XMR, since most of the larger gateways have quietly dropped it.
The fiat list is the biggest and nobody mentions it
Here is the list that never makes a headline and is the one most merchants actually need. Every gateway prices invoices in a fiat currency and converts at checkout, and that pricing list dwarfs every crypto list it has. BitPay carries 158 fiat pricing currencies against 21 crypto tickers. CoinGate's API marks 44 fiat priceable against 11 crypto. Plisio advertises conversion into "160+ world currencies", and NOWPayments' homepage panel offers 75+ fiat.
Three different jobs, three different lists. The pricing list decides whether you can quote a customer in their own money — biggest list, matters if you sell internationally. The acceptance list decides what a customer may hand over — the marketed list, matters least. The settlement list decides what lands in your account — smallest list, matters most. A merchant selling into forty countries and settling in one stablecoin needs a long first list and a one-item third list, and no gateway's headline number tells them whether they have it.
The pricing list also has a quiet cost attached. Quoting in a currency the gateway does not hold means a conversion at checkout at the gateway's own rate, and we measured what that spread costs earlier this month: up to 0.99% on top of the service fee, which is the same order as the service fee itself. A long fiat list is a feature you pay for per transaction rather than per month.
What to ask before you integrate
Five questions, in this order. None of them is answered by the number on the homepage, and all five can be answered before you create an account with at least four of the six gateways above.
- What can I settle in? Start here, not at acceptance. If the answer is not published without an account, treat that as the answer — two of our six would not tell us.
- Is the coin I want to keep on both lists? The CoinGate matrix above is the trap in miniature: take XRP at checkout and it converts on arrival, whether or not you meant it to.
- Are they counting assets or asset-chain pairs? Divide any headline figure by roughly 1.2 before comparing it with another company's, and ask for the list rather than the number.
- How many fiat currencies can I price in? This is the list that decides whether you can quote a German customer in euros, and it is the one nobody advertises.
- What does the payout list look like? If you also send money out — to contractors or suppliers — that is a fourth list, and on CoinGate it holds two assets that appear nowhere else.
One caveat, stated rather than buried. This is a single afternoon's snapshot, 24 September 2026, of six gateways out of a field of dozens, and these lists move — a coin gets delisted, a chain gets added, a settlement option opens in a new region. Nothing here should be read as a permanent ranking. What is durable is the structure: the lists are separate, the marketed number is the longest one, and the endpoint is checkable in ninety seconds. Re-run the four requests on the morning you sign and you will have better data than any comparison article, including this one.
Compare what a gateway actually gives you
We track service fees, rate spreads, invoice windows, settlement models and KYC requirements for every processor in the directory, so you can check the lists that matter against your own order book before you wire anything into a checkout. NOWPayments keeps its currency endpoint open to anonymous requests, which is more than half this field manages.
Compare Crypto Payment Gateways →FAQ
How many cryptocurrencies can a crypto payment gateway actually accept?
Far fewer than the homepage says, and the number depends on which list you mean. Counted from each company's own public endpoint on 24 September 2026: NOWPayments returned 224 tickers against a marketed 300-plus, and 38 of those 224 are the same asset on a second chain, leaving 186 distinct assets. BitPay's public currencies file carried 21 distinct crypto tickers against a marketed 100-plus. CoinGate's API marked 11 currencies payable, which matches the 10-plus it advertises. The marketed figure is almost always the acceptance list, which is the longest list a gateway has.
What is the difference between accepted currencies and settlement currencies?
Accepted currencies are what a customer may pay in. Settlement currencies are what the gateway will hand you afterwards, and the second list is always shorter. BitPay documents 15 crypto and 8 fiat settlement currencies against an advertised 100-plus accepted. CoinGate's API marks 11 currencies payable and 11 receivable, but they are not the same 11: you can be paid in XRP, TRON, BNB or Polygon and you cannot keep any of them. Check the settlement list before the acceptance list, because that is the one that constrains your treasury.
Why do gateways count the same coin more than once?
Because a token issued on six blockchains is six entries in an API and one asset to a customer, and nothing obliges a gateway to say which unit it is counting. NOWPayments' public currencies endpoint lists USDT ten times (TRC20, ERC20, BSC, Solana, Polygon, TON, Celo, Optimism and two Arbitrum variants) and USDC nine times. Across the whole list, 18 assets account for 56 tickers. OxaPay is the counter-example: it could advertise 31 coin-network pairs and instead shows 18 coins.
Which cryptocurrencies can I settle in with CoinGate?
Eight crypto and three fiat, verified against CoinGate's GET /v2/currencies response on 24 September 2026. The crypto settlement currencies are BTC, LTC, ETH, BCH, DOGE, USDC, SOL and EURC; the fiat are USD, EUR and GBP, over SWIFT with SEPA also available for EUR. Note the two asymmetries: Bitcoin Cash is settle-only and cannot be paid in, while XRP, TRON, BNB and Polygon are pay-only and cannot be settled in.
How many cryptocurrencies does BitPay support in 2026?
BitPay's marketing says over 100, from a resource page dated April 2024 that is still live. Its own public currencies file at bitpay.com/currencies returned 196 entries on 24 September 2026: 158 fiat pricing currencies and 38 crypto entries, which collapse to 21 distinct crypto tickers once the same token on Ethereum, Polygon, Arbitrum, Optimism, Base and Solana is counted once. Settlement is documented separately at 15 crypto and 8 fiat.
Can I check a gateway's supported currencies before I sign up?
With some, yes, and that is itself a signal. CoinGate (api.coingate.com/v2/currencies), NOWPayments (api.nowpayments.io/v1/currencies), BitPay (bitpay.com/currencies) and OxaPay (api.oxapay.com/api/currencies) all answer an unauthenticated request. Plisio's currencies endpoint returns 401 without a verified domain and key, and Cryptomus does not expose a public currency list at all, so its marketed figure of more than 100 cryptocurrencies cannot be checked from outside an account.
Which currency list should a merchant look at first?
The settlement list, then the payout list, then acceptance last. Acceptance breadth is mostly handled by conversion at checkout and costs the gateway little to extend, which is why it is the number in the headline. Settlement decides what actually reaches your treasury, and the payout list decides what you can send back out to suppliers or staff. On CoinGate, only 7 of the 14 crypto assets that appear anywhere in its own documentation appear on all four of its lists.
Affiliate disclosure: payyd.co earns a commission on sign-ups made through our /go/ links, including the NOWPayments link above. No gateway supplied, reviewed or saw these figures before publication. Method, so you can repeat it: every count was taken on 24 September 2026 from an unauthenticated request to the gateway's own endpoint — CoinGate /v2/currencies, NOWPayments /v1/currencies, BitPay /currencies and OxaPay /api/currencies — or, where no endpoint is public, from the company's own page on that date: NOWPayments supported coins, CoinGate accept crypto payments, BitPay settlement documentation, Plisio and Cryptomus. "Distinct assets" collapses chain variants of one token to a single entry. Where a company's own pages disagree with each other we print both rather than choosing.