Plan the payment handoff before launch.
Scope hosted checkout, widget embeds, webhooks, and platform work before production.
Plan the handoff before launch.
OmniPay reviews the intended payment path, checkout flow, webhook ownership, and operational handoff before launch.
- Confirm where the chosen hosted checkout collects payment details.
- Confirm where provider credentials are stored and which server-side route owns each request.
- Document webhook and reconciliation responsibilities before launch.
- Verify plugin or custom-route availability for the selected provider and platform.
Handoff checklist
Confirm the checkout path, responsible provider, payout questions, webhook events, and support ownership before launch.
Integration options
Choose the handoff that fits.
Hosted checkout, embedded widgets, server-side route requirements, webhooks, and platform work are reviewed against the merchant stack.
Hosted
Hosted checkout
Review provider-hosted payment flows and confirm where payment details are collected.
- UX scope
- Brand settings
- Security boundary
Server-side route
Server-side route requirements
Review route ownership, provider credential boundaries, and implementation responsibilities.
- Route plan
- Credential boundary
- Request shape
Events
Webhooks
Document the selected provider's event types, payload structure, retry behaviour, reconciliation, and replay expectations.
- Event map
- Retry plan
- Fulfillment guard
Platform
Commerce plugins
Check available commerce plugins and identify project-specific work only after the provider and platform are selected.
- Storefront fit
- Credential setup
- Order status sync