Payments APIs (2026): 10 Options Sorted by the Job You Need

Search for a payments API and you'll get a mix of card processors, bank payment specialists, cross-border transfer platforms and card issuers, all using the same words. The developer experience matters, but the bigger question is what the money needs to do inside your product.

This list sorts developer APIs by that job. It isn't a list of hosted checkouts or orchestration layers. The ten providers below are listed alphabetically and in no particular order, and every description comes from each provider's own website, read as of Oct 2026. If you want a ready-made checkout for a shop, my guide to payment gateways is the better starting point.

Payments APIs by job and main use

I checked the free plan column on each vendor's own website, as of Oct 2026. Yes means the page names a free plan, a free version or an open source edition. Trial only means the page names a time-limited free trial. Not stated means the page I read named neither, so check the vendor's own site before you sign up.

Tool	Type	Good for	Free plan
Adyen	Enterprise fintech platform	Payments, data and financial products together	Not stated
Checkout.com	Online and in-person payment services	High-performance card acceptance online and in person	Not stated
GoCardless	Bank payments and Pay by Bank	Recurring bank debits and Pay by Bank	Not stated
Marqeta	Card issuing and processing	Launching branded card programmes	Not stated
Mollie	Online and in-person payments platform	Payments, subscriptions and reconciliation in one place	Not stated
Plaid	Bank account connection and fintech APIs	Linking bank accounts, Pay by Bank and payouts	Not stated
Rapyd	Global payments and fintech infrastructure	Accepting and sending payments across many countries	Not stated
Stripe	Global payment processing platform	Accepting payments online through one global platform	Not stated
Unit	Embedded financial infrastructure	Accounts, cards and money movement inside your product	Not stated
Wise Platform	Cross-border payments infrastructure	Sending money internationally inside your product	Not stated

Ten payments APIs for developers and platforms

Adyen

Best for: Larger businesses wanting payments, data insights and financial products on one platform, with built-in optimisations for conversion and fraud.

Checkout.com

Best for: Enterprises focused on acceptance rates, with in-person payments at the point of sale now alongside online card processing.

GoCardless

Best for: Businesses moving recurring and one-off collection from cards to bank payments, with outbound supplier payments and agentic payments now on offer.

Marqeta

Best for: Companies launching their own card programmes that want enterprise-grade issuing and processing, with payment experts guiding the launch.

Mollie

Best for: Growing businesses wanting online and in-person payments, subscriptions, funding, reconciliation and fraud prevention without adding more providers.

Plaid

Best for: Fintechs that need to connect customers' bank accounts, then run Pay by Bank, recurring payments and payouts at scale.

Rapyd

Best for: Businesses selling across borders that want online and in-store acceptance, payouts and card issuing from one global provider.

Stripe

Best for: Developers and online businesses that want to start accepting payments quickly through one global processing platform, with sales help on hand.

Unit

Best for: Software platforms embedding accounts, cards and lending, with ACH, wire, check and real-time payments on a single native ledger.

Wise Platform

Best for: Banks and platforms adding international money transfers to their own product, with over 99% straight-through processing on transfers.

One phrase, four different payment jobs

Here's the thing most comparisons skip. A payments API can mean taking card payments, collecting from bank accounts, moving money across borders or issuing cards, and each provider's own page tells you which one it leads with. Plaid's page is about connecting bank accounts and moving money between them, and Marqeta's leads with card issuing and processing, not checkout.

Speed claims differ by job too. Wise reports that 78% of its instant payments take under 20 seconds and 96% arrive within 24 hours. That's a useful number for cross-border transfers and means nothing for card checkout, so compare like with like.

Match the API to what your money needs to do

• Accept payments. Cards and wallets online and in person. This is the classic processor job, where acceptance rates and fraud tools matter most.
• Collect from bank accounts. Recurring and one-off bank debits or Pay by Bank, which suits subscriptions and invoices.
• Connect accounts. Reading bank account details with consent, to verify a customer or start a bank payment.
• Move money. Payouts and international transfers to suppliers, sellers or staff.
• Issue cards. Your own branded debit, prepaid or credit cards for customers or employees.
• Embed banking. Accounts, cards and lending built into your own software.

Many products need two of these. A platform for freelancers might accept card payments from clients and send payouts to workers, so check whether one provider covers both or you'll be running two.

If you're a small business weighing simpler options, my comparison of payment processors for small businesses and my Stripe vs Square breakdown cover the everyday choices.

Developer questions to settle before you integrate

1. Job fit. Does the provider lead with the job you need, or is it a side feature?
2. Countries and methods. Which countries, local payment methods and bank schemes does it support where your customers are?
3. Licensing. Who holds the licence, and what compliance work stays with you?
4. Sandbox. Is there a sandbox and clear documentation so your developers can build and test before signing?
5. Payouts and reconciliation. How quickly do funds settle, and how easily can finance match payments to orders?

Do you make a payments API? Tool makers can ask to be considered for a featured place on this list.

My plain advice on picking a payments API

Write down the job first: accept, collect, connect, move or issue. Then shortlist only the providers whose own pages lead with that job, and build a small proof of concept in each sandbox before you sign. The API that feels easiest in week one isn't always the one that settles funds where you need them.

And plan for a second provider later. Many growing products end up with one API for card acceptance and another for bank payments or payouts, so keep your payment logic tidy enough to add one.

Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

Frequently asked questions

What is a payments API?

It's a set of endpoints that lets your software take, collect, send or manage money in code, instead of through a hosted page or a manual process.

Is a payments API the same as a payment gateway?

Not quite. A gateway is mainly about taking card payments at checkout. A payments API can also cover bank debits, account linking, payouts and card issuing.

What is Pay by Bank?

It's paying straight from a bank account through open banking instead of with a card, with the customer approving the payment in their own banking app.

Can one payments API do everything?

Some cover several jobs, such as acceptance, payouts and card issuing, but most lead with one. Check the provider's own page for what it's built around.

Do I need a licence to use a payments API?

Usually not for card acceptance, because the provider holds the licence. Card issuing and embedded banking tend to involve more compliance work on your side, so check each provider's terms for your country.