Start accepting payments
Check what is available
Capability review date: November 20, 2026. The confirmed merchant integration path covers creating, retrieving, listing and closing Checkouts, plus listing payment methods. A documented route does not grant your account or environment access. Confirm permissions with your onboarding contact before starting.
| Capability | Current position |
|---|---|
| Checkout payments | Merchant routes confirmed; confirm results through server-side queries |
| Payment details, refunds and Webhooks | Merchant availability pending confirmation; do not depend on them for launch |
| Settlement items and settlement queries | Merchant routes confirmed; execution support for creating settlements remains unconfirmed |
| Dashboard payment links, customers, products, subscriptions, invoices, quotes, teams, branding and reports | Planned workflows; public availability unconfirmed. Related instructions apply only to accounts with confirmed access |
| Corporate cards, fiat exchange and bank payouts | Availability unconfirmed; outside the current payment integration commitment |
Prepare and accept a first payment
- Identify the business entity, website, contact and assets you intend to accept. Prepare the information in onboarding and verification and confirm production access requirements.
- Assign owners for orders, support, funds and integration. One person may cover several roles, but refund approval and wallet changes need a named owner.
- Obtain credentials for the correct environment and check the asset, network and payment-method combinations actually returned. Do not enable networks from a promotional list.
- Have your integration owner create a payment request, persist its order-to-Checkout mapping and share the actual returned Checkout URL with the payer.
- Query from your server, verify the order, amount and currency, and fulfill once. A return page, screenshot or wallet showing “sent” cannot replace confirmation.
- In an authorized test environment, rehearse success, timeouts, duplicate payments and late funds. Define how support will receive refund requests while refunds remain unavailable, then decide your production scope.
You are ready when the order, payment result and fulfillment record are traceable and unresolved orders survive a service restart. Opening Checkout alone is not a completed integration.
Find a task guide
- Payments: Checkout and payment links, late, excess and insufficient payments.
- Funds: refunds, settlements, wallets, fees.
- Operations: customers, products and subscriptions, invoices and quotes, reports.
- Configuration: team access, keys, Webhooks and testing, branding, networks and risk, account security.
More business guides
Coupons · Corporate cards · Fiat services and bank reconciliation. Public availability remains unconfirmed; check each guide's prerequisites first.
Missing controls or failed actions
Check the account, test or production environment, permissions and feature availability. A missing menu does not establish that a plan upgrade is required. If a result is unknown, retain the original order and Checkout ID and resume querying. Give your contact the time, environment, error and available request identifier, without credentials or recovery information.