Launch checklist

• App profile name, icon, description, and app URL are correct.
• Test and live environments are configured separately.
• Required modules are enabled in test.
• App fee settings are reviewed and intentional.
• Support contact, privacy policy, and terms are available.

• Recipient payability is checked before purchase buttons appear.
• Checkout cancel URLs take buyers back to the app context.
• Browser returns show processing until ATM confirms status.
• Guest and signed-in buyer flows have been tested.
• Refund, subscription cancellation, and amount-change paths have been tested when used.

• Webhook signatures are verified with raw request bodies.
• Handlers deduplicate delivery ids before side effects.
• Failed delivery redrive has been tested.
• Event handlers are environment-aware.
• XRPC receiver callbacks are optional and tested only if enabled.

• Dashboard delivery logs are monitored during the first real checkouts.
• App order ids are stored with ATM payment ids.
• Customer data is stored only where needed for fulfillment.
• Error states are friendly when payment setup or inventory is unavailable.
• Support has a path to inspect ATM payment ids and app order ids.

Move one app and one payment flow at a time. Keep test mode available after launch so agents and app developers can continue testing new features safely.