Choose your collection flow
A payment link creates a fresh CheckoutSession when a buyer opens it. Catalog
products and prices can be reused across checkout, links, and subscriptions.
Payments for connected accounts
A platform uses its own keys and selects the connected account on each request. That merchant owns the PaymentIntent, SetupIntent, customer, and saved payment method, and the same merchant ID is used on your server and in the browser. See How Connect works.After submission
Create one PaymentIntent for each payment. If a response is lost, retrieve that PaymentIntent before creating another. A redirect or browser callback updates the customer’s screen; verified server-side state determines fulfillment. For saved cards, verify that the SetupIntent succeeded and belongs to the expected merchant and customer before storing its payment method ID.What’s next
Reliable API requests
Retry safely and recover when a response does not arrive.
Ways to accept payments
Compare hosted checkout, Ionic Blocks, and terminals side by side.
Handle webhook events
Verify each event’s signature and fulfill orders from it.