Go-live checklist

Before launch, switch the configuration you validated in test mode over to production, and make sure your business systems treat webhook results as the source of truth.

Confirm before going live

• A live API key has been created.
• Server environment variables use the live API key.
• The webhook URL points to your production domain.
• The webhook signing secret has been updated in the production environment.
• No API key is exposed in the frontend.
• successUrl and cancelUrl point to your production website.
• Fulfillment, shipping, membership activation, and invoicing only run after payment confirmation.

Handling order statuses

Your system should handle at least these statuses:

Status	Recommended action
requires_payment	Wait for the buyer to enter the checkout page
processing	Payment in progress — do not fulfill yet
confirmed	Mark as paid and fulfill
failed	Let the buyer retry the payment
refunded	Sync support and finance records
expired	Create a new payment order

Your first live order

After going live, verify with a small order first:

1. Your server creates the order.
2. The buyer can open the checkout page.
3. The webhook is delivered after payment.
4. The order status updates correctly in your system.
5. The record appears under Transactions in the merchant dashboard.

When something goes wrong

Have these ready for investigation:

• paymentId
• Your merchant order ID orderId
• The webhook delivery id
• The transaction hash
• The relevant window of your server logs

Continue reading: Troubleshoot payment issues