| name | setup-curlec |
| description | Set up, build, debug, review, and explain Razorpay Curlec payment gateway integrations using Curlec and shared Razorpay documentation. Use when working with Curlec/Razorpay Standard Checkout, FPX or redirect payment methods, Orders API, Payments API, Refunds API, Payment Links, Basic Auth API keys, checkout.js options, callback_url, payment signature verification, webhook setup, webhook HMAC validation, sandbox/test mode, payment capture, payment status reconciliation, or Malaysia payment gateway go-live checks. |
Curlec Payment Gateway
Use this skill for Razorpay Curlec payment gateway integration work.
Source
Read references/curlec-payment-gateway.md before giving factual API guidance or writing integration code. It contains source URLs, integration flow, endpoint map, signature rules, webhook rules, sandbox notes, and common failure fixes from Curlec docs.
Read references/account-setup.md when user asks how to register, which API keys are needed, where credentials come from, or what dashboard setup is required.
Core Workflow
- Identify product surface: Standard Checkout, redirect/FPX flow, Payment Links, Orders/Payments/Refunds API, mobile SDK, plugin, or payout/RazorpayX.
- Identify environment: Test mode or Live mode. Keep keys, orders, webhooks, and dashboard checks separated by mode.
- Create an internal transaction/order row first, then create a Curlec Order server-side.
- Pass only the public Key ID and Curlec
order_id to Checkout. Keep Key Secret server-side only.
- On Checkout success, store
razorpay_payment_id, razorpay_order_id, and razorpay_signature, then verify the signature on the server.
- Use webhooks for durable asynchronous fulfilment and API fetches for immediate user-facing confirmation where needed.
- Before fulfilment, verify amount, currency, order mapping, payment status, capture state, signature, idempotency, and duplicate events.
