Can I vibe code PayU?

1. GOAL: Build a payment integration service in Node.js/TypeScript for a commerce engine that routes checkout intents to multiple payment processors (e.g., Stripe, PayU, PayPal), processes asynchronous webhooks, and maintains an immutable transaction ledger.

2. DATA MODELS:
- PaymentIntent: id, order_id, amount, currency, status (pending, processing, succeeded, failed), gateway_name, gateway_transaction_id, metadata (JSONB), created_at.
- TransactionLedger: id, payment_intent_id, type (authorization, capture, refund, chargeback), amount, gateway_response (JSONB), status, timestamp.
- WebhookLog: id, gateway, event_type, payload (JSONB), processed (boolean), retry_count, received_at.

3. CORE API ENDPOINTS:
- POST /api/v1/payments/create-intent: Accepts order_id, amount, currency, country_code. Selects gateway based on country_code. Returns processor-specific client token or checkout redirect URL.
- POST /api/v1/payments/webhooks/:gateway: Validates cryptographic request signature (HMAC). Pushes event to a background Redis queue for processing.
- POST /api/v1/payments/:id/refund: Initiates refund flow via processor client API and logs ledger entry.

4. FAILURE MODES & EDGE CASES:
- Idempotency: Webhook consumer must process each event exactly once based on gateway transaction ID.
- Signature Verification: Immediately reject unsigned or invalidly signed webhooks prior to parsing payload.
- Database Transactions: Ledger writes must run inside ACID database transactions to prevent partial updates.
- Out-of-Order Events: Handle cases where payment.succeeded webhook arrives before payment.created callback finishes.

5. OUT OF SCOPE:
- Do NOT store or process raw card numbers (PANs) or CVVs to avoid PCI-DSS scope.
- Do NOT build card tokenization logic; delegate entirely to gateway client SDKs.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs