Getting Started with Payment APIs
How full-stack processors, merchant-of-record platforms, and orchestration layers differ, and what to compare when choosing a payment API.
By FintechToolkit Editorial Team · Methodology 1.0
A payment API decides which payment methods and markets a product can support. Changing provider later means rebuilding checkout, migrating stored payment credentials, and re-testing reconciliation, so the choice is easier to make against written requirements than to reverse. The main differences between providers are the acquiring model, market coverage, and who carries tax and compliance obligations.
Full-stack processors
Stripe offers card and local payment acceptance, subscription billing, marketplace payouts through Connect, and fraud screening through Radar behind one API, with official server-side SDKs and a test mode available at sign-up.
Adyen runs online and in-person payments on a single platform and targets larger merchants that want control over authorisation and routing across payment methods and markets. Checkout.com is also aimed at enterprise merchants, with card acquiring and alternative payment methods across many markets.
Regional processors trade breadth for local depth: Mollie focuses on European payment methods, and Razorpay on payments in India. Airwallex combines acceptance with multi-currency accounts and cross-border payouts.
Merchant of record
Paddle and Lemon Squeezy act as merchant of record: they are the legal seller to the end customer and handle sales tax and VAT registration, collection, and remittance. Fees are higher than raw processing, and the provider rather than the product holds the customer payment relationship.
Orchestration
Hyperswitch is an open-source payment orchestration layer that routes transactions across several processors behind one integration. Orchestration adds a component to operate and, alongside it, processor redundancy and routing control.
Money movement beyond acceptance
Accepting payments and moving money are separate problems. GoCardless collects recurring payments by bank debit. Modern Treasury and Moov handle payment operations such as ACH transfers and payouts, and Formance provides an open-source ledger for tracking balances across them. Brex covers corporate cards and spend management rather than checkout.
How to choose
Start from markets and payment methods: list the countries and local methods the product needs, then check which providers support them directly. Next decide who should be the seller of record, since that settles tax handling. Then compare webhooks, idempotency, error codes, refunds, and dispute handling in a sandbox, where providers differ more than their documentation shows. Commercial terms come last, because they are negotiable and the integration constraints are not.
Editorial note
This guide explains evaluation considerations and links to directory records. It does not constitute legal, compliance, procurement, or investment advice. Use the linked primary sources to validate time-sensitive details.
Tools covered in this guide
- StripeFull-stack payments platform for accepting payments, managing subscriptions, and running marketplaces.

- AdyenSingle global platform for card acquiring, local payment methods, and unified commerce.

- Checkout.comEnterprise payment processing with direct acquiring and granular authorisation control.

- PaddleMerchant of record for software companies — billing, sales tax, and compliance handled.

- Lemon SqueezyMerchant of record for digital products, with checkout, subscriptions, and tax handled.

- HyperswitchOpen-source payment orchestrator that routes across multiple processors.

- GoCardlessBank debit and open banking payments for recurring and invoice collection.

- BrexSpend management and corporate cards API for venture-backed and enterprise companies.
