Payment Gateway Integration
integrating-payment-gateways
Patterns for connecting payment providers (Stripe, etc.) with Appwrite. Use for handling secure transactions and updating booking status.
SKILL.md
Full skill instructions
Payment Gateway Integration
When to use this skill
- When implementating actual "checkout" flows.
- When an order status needs to change from "pending" to "paid".
Architecture
- Client: Redirect user to payment provider (Stripe Checkout).
- Provider: Sends a Webhook back to your Appwrite Function or Route Handler upon success.
- Server: Verifies the webhook signature.
- Database: Updates the booking document in Appwrite.
Rules
- Never Store CC Info: Use tokens/checkouts provided by the gateway.
- Idempotency: Ensure that receiving the same webhook twice doesn't result in double bookings.
Instructions
- Test Mode: Always use "Sandbox" or "Test" keys during development.
- Logs: Keep detailed logs of webhook transactions for debugging.
