How Payment Processing Works
Every card payment moves through the same core cycle. You request an authorization to confirm funds are available, request a capture to transfer those funds to your account, and can void or refund the transaction afterward if needed.
See the Payments Overview for the full picture of institutions, card types, and transaction types involved.
Explore the Payment Center
View and manage payment activity, and store customer information, directly in the Payment Center.
Transactions
Take payments, capture authorizations, refund and void transactions, and review fraud-held transactions.
Explore TransactionsInvoices
Create, edit, send, and cancel single-item and itemized invoices.
Explore InvoicesPay by Link
Create, activate, edit, and share payment links across digital and physical channels.
Explore Pay by LinkSubscriptions
Create recurring billing subscriptions and manage their status.
Explore SubscriptionsCustomers
Store customer information, process transactions quickly, and manage recurring billing.
Explore CustomersPayments Essentials for Developers
Get Started with Payments
Test your Standard Payment Processing integration using test credentials, test card numbers, and test amounts.
Get startedEndpoints: Payments
Consolidated reference of the REST API endpoints used across the payments guide, grouped by functional area.
View endpointsAuthorizations
Authorize payment transactions using the Standard Payment Processing API. Includes required fields, country-specific fields, and REST examples.
View guideCaptures
Capture authorized payment transactions to transfer funds to the merchant account.
View guideSales
Process single-message payment transactions (sale) that authorize and capture in one request.
View guideRefunds
Process follow-on refunds linked to a prior authorization or capture.
View guideStand-Alone Credits
Process a stand-alone credit that is not linked to a capture or sale.
View guideVoids
Void a capture or credit transaction before it settles.
View guideChoose How to Process a Payment
Most integrations use one of two request patterns, and some processors require one over the other.
| Feature | Authorization + Capture | Sale |
|---|---|---|
| Best for | Orders fulfilled later, such as shipped goods | Orders fulfilled immediately, such as digital goods or services |
| Request shape | Two requests: authorize, then capture | One request: authorize and capture together |
| When funds move | At capture, not at authorization | Immediately |
| Guide | Authorizations and Captures | Sales |
Explore Payment Features
Beyond the core transaction lifecycle, the payments API supports these features for compliance, cost, and fulfillment needs.
Debit and Prepaid Card Payments »
Authorize debit and prepaid card transactions with partial authorization support.
Payer Authentication (3-D Secure) »
Shift chargeback liability to the issuer and satisfy PSD2 Strong Customer Authentication (SCA) requirements.
Replace primary account numbers with tokens to reduce PCI DSS scope.
Route eligible transactions through the lowest-cost available path using single-message processing.
Split one order into multiple shipments and captures when items become available over time.
Get real-time worldwide tax calculation for a transaction before you authorize it.
Thanks for your feedback!
Last published: September 29, 2026