Cashfree Payment Gateway - Payment Links

Send a POST request to /pg/links with link_amount, link_currency, link_purpose, and customer_details.customer_phone, authenticated with x-client-id and x-client-secret headers. The response returns a link_url you can share with the customer, plus a base64 QR code.

Verify the HMAC signature using the raw body and x-webhook-timestamp header, then read link fields flat under data — there is no data.link wrapper. Dedupe on (cf_link_id, link_status, link_amount_paid) since delivery is at-least-once, and note that data.order is null for CANCELLED and EXPIRED transitions.

Yes, set link_partial_payments to true and optionally link_minimum_partial_amount. Each installment creates a separate PG order, and the link status moves from PARTIALLY_PAID to PAID once link_amount_paid equals link_amount.

Refund the underlying PG order, not the link itself. Call GET /pg/links/{link_id}/orders?status=ALL to find paid order_ids, then POST to /pg/orders/{order_id}/refunds and listen for the REFUND_STATUS_WEBHOOK.

SMS notifications are disabled in the Cashfree sandbox environment by design; only email notifications fire there. Test SMS delivery in production using a small link_amount and a disposable customer_phone number.

Use payment links for one-off or ad-hoc collections like invoices, rent, or freelance fees where building a checkout is overkill. For high-volume integrated website or app checkouts, use the core PG APIs and SDKs; for recurring billing, use subscriptions instead.