Skip to main content
Test mode and live mode are separate for platforms just as they are for merchants. Connections, customers, keys, domains, webhook endpoints, and object IDs exist in one mode only, so a launch recreates your live configuration and verifies each flow your merchants will use. Complete the steps every integration shares in Going live as well.

​
Launch checklist

1

Prove each flow in test mode

Run every flow your platform offers against a connected test merchant: onboarding, payments, saved cards, refunds, and webhook handling. Test configurations use Connect only, so a test merchant can take test payments as soon as it agrees to connect. See Start in test mode.
2

Create a live onboarding configuration

In Connect → Onboarding → Links, create a live configuration with Connect + live application, a pricing plan, and the permissions your flows need. Live return URLs use HTTPS on a domain listed under Connect → Domains.
3

Create live platform keys

In Connect → API keys, create live keys with the same permissions as your test keys. Keep the secret key in your secret manager. Only the publishable key belongs in the browser.
4

Register live payment domains and wallets

Register each payment website under Connect → Domains in live mode, and enable Apple Pay or Google Pay for each live domain your pages use. See Platform payment domains and Wallet setup for platforms.
5

Register live platform webhook endpoints

Create your connected-accounts endpoint again with a live platform key and store its new signing secret. See Webhooks for platforms.
6

Onboard live merchants

Each merchant completes the live application. Wait for payments_enabled before taking live payments for that merchant. See Know when payments are enabled.
7

Verify with real transactions

For one live merchant, run a real, low-value payment, confirm it, and refund it. Before recording saved cards, verify one live SetupIntent for the intended merchant and customer. Run acceptance testing on an Ionic-assigned physical test terminal before a merchant uses production hardware.

​
What changes for each merchant

Each receiving merchant needs an active live connection that grants the permissions your integration uses. Live requests use the merchant’s live customer and payment IDs. Match event.account on every live webhook event to the merchant stored with the payment. See Launching a Connect integration.

​
What’s next

Read the full go-live guide

Follow every launch step for Ionic accounts and Connect integrations.

Use test cards

Rehearse approvals and declines before live traffic.