Skip to content

Post-v1 external resilience and UPI soak #22

Description

@Phloraxx

External integrations

  • Configure PAYGATE_BACKUP_S3_* with a real off-server S3-compatible destination.
  • Verify scheduled archive creation, remote upload, archive verification and temporary restore drill from the remote backup.
  • Configure OPERATOR_ALERT_WEBHOOK_URL and OPERATOR_ALERT_WEBHOOK_SECRET with a real monitoring/notification destination.
  • Test open, retry, recovery and resolved alert delivery without exposing secrets or bank evidence.

Multi-day production soak

Run controlled real payments over at least seven days across available UPI apps and record only anonymized timing/outcome metrics:

  • Google Pay
  • PhonePe
  • Paytm
  • BHIM or another bank app
  • phone temporarily offline, then catch-up
  • SMS delivered after checkout expiry while bank transaction occurred before expiry
  • duplicate provider event
  • wrong amount / missing reference review path

Record transaction-to-SMS and SMS-to-verification latency, match outcome and connector state. Do not record SMS bodies, payer names, VPAs or session credentials in the issue.

Exit criteria

  • Remote backup survives simulated loss of the local Docker volume.
  • Critical connector/backup alert reaches the external destination and resolves cleanly.
  • No unexplained missed or incorrectly assigned payment during the soak.
  • Quarantine remains 24 hours unless measured evidence supports a safer value.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions