Payment Gateway Integration API 2026: How to Pick One (Stripe, PayPal, NOWPayments, BTCPay)

Choosing a payment gateway API in 2026

For most of the last decade the developer answer to "which payment gateway API should I use" was "Stripe, unless you have a specific reason not to." That advice was correct because Stripe was the only API-first processor with first-class SDKs, a real sandbox, idempotency primitives, and dashboards your finance team could actually use. The alternatives (PayPal, Authorize.Net, Braintree) all felt like 2010 tooling wearing a 2025 wrapper.

In 2026 the calculus has shifted. Crypto payment APIs have matured to the point where NOWPayments and BTCPay Greenfield ship developer experience that is within striking distance of Stripe, at a tenth of the cost and with zero geographic restrictions. Square has improved its API but still feels in-person-first. PayPal's developer experience has not meaningfully improved since Braintree was acquired in 2013. So the right framing for a new build in 2026 is not "Stripe or not" but "which combination of these five APIs do I integrate, and why."

This guide scores five gateway APIs on the dimensions that actually matter to backend engineers: integration time, authentication model, webhook signing quality, idempotency support, sandbox parity, SDK count, and headline fee. Then it gives use-case verdicts (SaaS, marketplace, international, high-risk). If you have already decided you want crypto only, jump to the narrower crypto-only API comparison and the broader crypto payment API guide.

The 5-API shortlist (scored)

Every gateway in this table is genuinely a credible 2026 pick for at least one use case. The scores are payyd's editorial assessment from integrating each API on real projects. "Integration time" is the working invoice plus verified webhook on a vanilla Node or Python server.

API	Tier (payyd)	Fee	Integration time	SDKs
Stripe	Not tiered (fiat-only)	2.9% + $0.30	~30 min	7 official
PayPal / Braintree	Not tiered (fiat-only)	2.59% – 3.49%	1 – 2 hours	6 official, fragmented
Square	Not tiered (fiat-only)	2.6% + $0.10 in-person	~45 min	6 official
NOWPayments	Gold	0.5%	~10 min	4 official
BTCPay Server	Bronze	0%	~20 min (post-install)	Community: JS, PHP, Python, Ruby, Go

Stripe, PayPal, and Square are not in payyd's tier system because payyd ranks crypto payment gateways. They are included here as the fiat reference points every developer evaluates against. NOWPayments and BTCPay carry their normal payyd tiers.

Dimension	Stripe	PayPal	Square	NOWPayments	BTCPay
Auth model	Bearer secret key	OAuth2 client_credentials	Bearer access token	x-api-key header	API key (Greenfield)
Webhook signing	HMAC-SHA256 + timestamp	RSA cert chain	HMAC-SHA256	HMAC-SHA512	HMAC-SHA256
Idempotency	Idempotency-Key header (24h)	PayPal-Request-Id	idempotency_key in body	Via payment_id natural key	Via orderId natural key
Sandbox parity	Full (test mode flag)	Separate sandbox.paypal.com	Full sandbox subdomain	Full sandbox.nowpayments	Full (Bitcoin regtest)
Crypto support	Via extension only	Limited (PYUSD, BTC)	No	300+ coins native	BTC + altcoins native

Stripe API: the incumbent (when it still wins)

Stripe is the gold standard for fiat-card payments and we will not pretend otherwise. The reasons are obvious to anyone who has integrated it: stripe.PaymentIntents.create() works the same way in Node, Python, Ruby, PHP, Java, .NET, and Go. The Idempotency-Key header is built into every mutating endpoint, so retries are safe by default. Webhook signing uses a timestamp-prefixed HMAC that prevents replay attacks. The sandbox is the same code path as production, just toggled by a key prefix, so there is no environment drift to debug.

Stripe also owns the surrounding tooling. Stripe CLI lets you forward webhooks to localhost during development. Stripe Tax handles VAT and US sales tax automatically. Stripe Radar plugs in fraud scoring at no extra config. For a SaaS that sells in USD to US customers, the integration economics are essentially "spend 30 minutes, ship a paying product."

Where Stripe loses: high-risk verticals (adult, gambling, some crypto-adjacent businesses, firearms, CBD in many states), which it bans under its Acceptable Use Policy. International FX, which costs roughly 2% on top of the 2.9% card fee for non-USD presentment. High-ticket sales where the percentage-based fee starts to hurt (a 10,000 dollar SaaS contract gives Stripe 290 dollars and the merchant 9,710). And anything where the customer specifically wants to pay in crypto, which Stripe addresses only through a Crypto extension (Pay With Crypto) that converts at checkout to USD before settlement, not a native crypto rail. For those use cases see our Stripe vs crypto gateways comparison.

PayPal and Square: fiat alternatives

PayPal / Braintree. The PayPal API surface is the most fragmented of the five. There is the original NVP/SOAP API (deprecated but still everywhere), the REST Orders v2 API, the Subscriptions v1 API, the Braintree Drop-In SDK (a separate product PayPal acquired), and PayPal Checkout JS (a browser SDK that wraps Orders v2). They all do similar things slightly differently. Authentication is OAuth2 client_credentials, which means an extra round trip on every workflow that has not cached the token. Webhook signing uses RSA verification against a published cert chain at api.paypal.com/v1/notifications/verify-webhook-signature, which is cryptographically sound but slower than HMAC and more bureaucratic to implement.

PayPal still wins one thing: consumer mindshare. For B2C marketplaces, gaming, freelance platforms, and secondhand commerce, a meaningful slice of buyers will only check out if PayPal is offered. The 2.59 to 3.49 percent fee reflects that demand. For B2B and SaaS we would skip it.

Square. Square is in-person-payments-first. Its API has improved dramatically since the 2022 rebuild, the Square Node SDK is genuinely pleasant, idempotency uses idempotency_key in the body of every mutating request, and webhook signing is HMAC-SHA256. But the headline fee structure (2.6% + 10 cents in-person, 2.9% + 30 cents online) is identical to Stripe online and Stripe is the better online tool. Square also charges 5 dollars per wire payout, which is silly in 2026 when ACH is free at every competitor. We recommend Square only if you also need its point-of-sale hardware and ecommerce in the same dashboard.

NOWPayments API: the crypto challenger

NOWPayments [Gold tier] is the crypto API closest in spirit to Stripe. The REST endpoints follow predictable verb-noun patterns (POST /v1/invoice, POST /v1/payment, GET /v1/payment/{id}), authentication is a simple x-api-key header (no OAuth dance), the sandbox at sandbox.nowpayments.io mirrors production with the same key format, and webhook signing uses HMAC-SHA512 over the JSON body in the x-nowpayments-sig header.

The four official SDKs (Node, Python, PHP, Java) wrap the REST API cleanly, and the documentation is the best in crypto payments. Where Stripe takes 30 minutes for a working invoice, NOWPayments takes about 10 because the surface area is smaller (you do not need to handle 3DS, address verification, or PCI compliance, the crypto rail does not have those concepts).

The trade-offs: only crypto, no fiat card option (which is exactly what you want if you are building for crypto-native customers, but a non-starter if you need to accept US cards). Idempotency works via the payment_id NOWPayments returns rather than a dedicated header, you persist that id against your internal order_id immediately and dedupe webhook events by it. The fee is 0.5% flat, which on a 10,000 dollar sale is 50 dollars vs Stripe's 290. Full review at NOWPayments review, sign-up via /go/nowpayments.

BTCPay Greenfield: full sovereignty

BTCPay Server [Bronze tier] is the open-source self-hosted option. The HTTP API is called Greenfield, it follows REST conventions with /api/v1/stores/{storeId}/invoices as the canonical endpoint, and authentication is an API key with scoped permissions (you can mint a key that only creates invoices, for example). Webhook signing is HMAC-SHA256 with a per-store secret. The sandbox is Bitcoin regtest, which is a full-parity local Bitcoin network you can run on your laptop, so you can test the entire confirmation flow without spending real BTC.

The integration time is about 20 minutes once your BTCPay instance is running. The catch is that running the instance itself takes 30 to 60 minutes on a 5 dollar VPS (see our BTCPay setup guide). Once it is up, the API is rock solid and the trade-off is clear: zero fees, full custody of your funds, no central operator that can deplatform you. Bronze tier in payyd's system because the lack of hosted support and SLA makes it the wrong call for non-technical merchants, but for sovereignty-conscious developers it is the right answer. Review: BTCPay Server.

Code snippets: same invoice, 3 different APIs

The clearest way to compare APIs is to look at the same task in each. Below are three implementations of "create a 100 dollar invoice." Notice the surface area difference, Stripe and NOWPayments are nearly identical in line count, BTCPay needs the store id but is otherwise comparable.

Stripe (Node SDK):

import Stripe from "stripe";
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY);

const session = await stripe.checkout.sessions.create({
  mode: "payment",
  payment_method_types: ["card"],
  line_items: [{
    price_data: {
      currency: "usd",
      product_data: { name: "Pro plan, 30 days" },
      unit_amount: 10000, // $100.00 in cents
    },
    quantity: 1,
  }],
  success_url: "https://yoursite.com/success?session_id={CHECKOUT_SESSION_ID}",
  cancel_url: "https://yoursite.com/cancel",
}, {
  idempotencyKey: `order_${userId}_${Date.now()}`,
});

return { checkout_url: session.url };

NOWPayments (curl):

curl -X POST https://api.nowpayments.io/v1/invoice \
  -H "x-api-key: $NOWPAYMENTS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "price_amount": 100,
    "price_currency": "usd",
    "pay_currency": "usdttrc20",
    "order_id": "order_abc123",
    "order_description": "Pro plan, 30 days",
    "ipn_callback_url": "https://yoursite.com/webhook/nowpayments",
    "success_url": "https://yoursite.com/success",
    "cancel_url": "https://yoursite.com/cancel"
  }'

# Response includes invoice_url to redirect the customer to

BTCPay Server Greenfield (curl):

curl -X POST https://btcpay.yourdomain.com/api/v1/stores/$STORE_ID/invoices \
  -H "Authorization: token $BTCPAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "100",
    "currency": "USD",
    "metadata": {
      "orderId": "order_abc123",
      "itemDesc": "Pro plan, 30 days"
    },
    "checkout": {
      "redirectURL": "https://yoursite.com/success",
      "redirectAutomatically": true
    }
  }'

# Response includes checkoutLink for the customer

Notice three things. First, all three return a hosted checkout URL you redirect the customer to, none of them require you to handle card data or wallet UX directly. Second, idempotency is explicit in Stripe (header), implicit via natural key in NOWPayments (order_id) and BTCPay (orderId metadata). Third, none of these is meaningfully harder than the others, the perceived difficulty of crypto APIs is largely a myth left over from 2018.

Fees compared on $100 / $1k / $10k sales

Headline percentages bury the actual dollars. Below is the merchant cost on three sale sizes, assuming a US card transaction for Stripe/PayPal/Square and USDT-TRC20 for NOWPayments/BTCPay (the most common high-value crypto flow because TRC-20 network fees are roughly 1 dollar regardless of transaction size).

API	$100 sale	$1,000 sale	$10,000 sale
Stripe	$3.20 (3.2%)	$29.30 (2.93%)	$290.30 (2.9%)
PayPal	$3.79 (3.79%)	$34.90 (3.49%)	$349.00 (3.49%)
Square (online)	$3.20 (3.2%)	$29.30 (2.93%)	$290.30 (2.9%)
NOWPayments [Gold]	$1.50 (0.5% + $1 net)	$6.00 (0.5% + $1 net)	$51.00 (0.5% + $1 net)
BTCPay Server [Bronze]	$1.00 (network only)	$1.00 (network only)	$1.00 (network only)

At 10,000 dollar tickets the gap between Stripe (290 dollars) and NOWPayments (51 dollars) is enough that a single B2B SaaS contract pays for the entire crypto integration in fee savings. At 100 dollar tickets the absolute dollars are small enough that developer-experience preference often wins. The crossover is roughly the 500 dollar AOV mark, see the deeper crypto payment API guide for per-feature breakdowns.

Pick by use case

FAQ

Affiliate disclosure: payyd.co earns a commission when readers sign up for NOWPayments through our /go/nowpayments link. We do not earn anything from Stripe, PayPal, Square, or BTCPay Server, and we recommend each of them above when they are the right fit for the reader's use case (Stripe for US-card SaaS, BTCPay for sovereignty-first builders). Our gateway tiering is based on payyd's editorial criteria, not commission rates.