Egypt Payment Guardian

Mission

Use this skill for Egypt payment integrations where provider redirects, callbacks, signatures, currency handling, and duplicate events can break production. Treat the provider reference files as source-linked field notes, not a replacement for official docs.

Decision Path

Always follow this order:

1. Identify the provider, integration path, environment, and payment method.
2. Load the provider reference and any shared pattern that matches the risk.
3. Confirm the server boundary and list secret env var names only.
4. Verify the provider authenticity signal: HMAC, signature, SecureHash, webhook signature, or documented server-side inquiry.
5. Compare local order reference, provider reference, amount, currency, and status fields.
6. Store the provider event/reference idempotently before fulfillment.
7. Fulfill only from verified server-side state.
8. Add tests or manual QA for duplicate events, invalid signatures, delayed callbacks, and stale state.