10. Prepare for production
Verify identity, payout, security, recovery, and catalog behavior before release
Before public release, verify the purchase path under both normal and failure conditions. Complete dashboard forms alone do not prove that the integration is ready.
Account and finance
- Identity verification is approved.
- A developer-owned IBAN is registered and approved.
- The gateway or store path and settlement lifecycle are understood.
Catalog and presentation
- Every product has the correct app identifier and price.
- Every product is attached to the intended entitlement.
- The default offering contains complete packages.
- The intended paywall version is published.
- Targeting rules preserve a valid fallback path.
Security and connection
- App keys match their app and environment.
- Secrets exist only on trusted servers.
- Customer identity survives sign-in and reinstallation.
- Logs do not expose tokens, credentials, or full gateway payloads.
Final tests
- Success, cancellation, network failure, and retry are covered.
- Restoration, renewal, and entitlement expiry are verified where applicable.
- Dashboard payment and entitlement state match app behavior.
- The team knows which non-sensitive identifiers to collect for support.
When every item is confirmed, the baseline setup is complete and the step-specific screenshots can be added to these pages.
Continue reading
Use the REST API documentation for server communication and Implementation for deeper concept guidance.