Choose an online payment workflow
Choose how to collect a payment method, submit the payment and support future billing.
Choose the collection experience
Use the Payment Component for a new embedded checkout and Hosted Checkout for a hosted experience. An existing Collect.js integration has its own migration considerations. Choose based on the product workflow and the confirmed merchant configuration. Product need Portal path Checkout embedded in your product Payment Component and backend integration. Hosted payment experience Hosted Checkout. Store a method for later use Customer Vault and consent workflow. Repeat billing on a schedule Recurring billing and failure handling. Maintain an existing token collection flow Collect.js and migration.
Separate token collection from processing
The browser collects and tokenizes payment details. Your server owns the order amount, private API credentials and payment submission. A tokenization callback is not a completed charge. online
Decide when money should be collected
Use a sale when the workflow is ready to authorize and capture together. Use authorization followed by capture when the collection decision belongs to a later fulfillment step. Track the gateway payment ID in either case. Confirm the selected payment methods and processor route. Define the point at which the order may be fulfilled. Choose sale or a separate authorization/capture workflow. Plan reversals, failed attempts and settlement reconciliation.
Extend the workflow deliberately
Saved methods, subscriptions, ACH and wallets introduce their own setup and customer-experience requirements. Confirm feature activation before displaying those options. A one-time payment token is not a reusable Customer Vault identifier. Recommended planning: agree consent, cancellation and support ownership alongside the technical integration so the product can handle the complete customer lifecycle.