Integration checklist

Use this checklist before asking OpenPoly to enable production traffic.

Build

• Implement backend call to POST /api/operator/launch.
• Store operator API key in server-only secret storage.
• Implement wallet adapter paths:
  • GET /balance
  • POST /debit
  • POST /credit
  • POST /debit-reversal
• Implement webhook receiver with signature verification and replay protection.
• Map operator user identity to stable external_user_id.
• Support product: "polyflight" in the launch request while preserving omitted-product Opinion behavior.
• Accept all documented mini_app_polyflight_* wallet reasons and additive native metadata.
• Subscribe to and deduplicate the complete mini_app.polyflight.* event catalogue.

Configure

• Create operator API key with only needed scopes.
• Configure allowed Mini App launch host in operator dashboard.
• Configure wallet adapter base URL and auth secret in operator dashboard.
• Configure webhook endpoint URL, event subscriptions, and webhook secret.
• Confirm market visibility mode and any allowlist or blocklist rules.
• If Polyflight is enabled, assign its read scopes explicitly and confirm current terms/settlement timezone.

Validate

• Launch Mini App from operator backend with test user.
• Confirm launch token redemption works only once.
• Confirm wallet adapter debit, credit, and reversal are idempotent.
• Confirm ambiguous primary mutations stop for manual review rather than being replayed automatically.
• Confirm webhook receiver accepts valid signature.
• Confirm webhook receiver rejects bad signature and stale timestamp.
• Confirm failed webhook delivery retries and can be replayed.
• Confirm staging drills pass before production cutover.
• Confirm Polyflight purchase/payout uses native IDR without Opinion FX.
• Reconcile a Polyflight win, loss, full refund, compensation, and manual-review case through operation, event, statement, and export.
• Verify positive, negative, and zero signed-position examples.

Production gate

• Secret rotation runbook prepared.
• On-call owner for wallet adapter and webhook receiver assigned.
• Logging redacts API keys, launch tokens, webhook secrets, and wallet secrets.
• Manual-review and compensation paths understood by operator support team.
• Polyflight liability, statement, payment, reconciliation, and safe-entry-disable paths understood.
• Staging simulator evidence kept separate from real external-wallet contract certification.
• Separate explicit production authorization recorded before deployment, enablement, or production wallet activity.