Skip to main content
GET
Retrieve Payment Link

Overview

Returns one payment link: its status, the payments made through it, its expiry_date, buyer, product, invoice and settlement. Use it to confirm a link’s outcome — for an active link it checks for a payment before answering, so it can be ahead of List Payment Links.

Path Parameters

  • link_id: The link’s ID from Create Payment Link, e.g. PR4829301756. The payment_id it returned is the same value.
From a payment webhook, pass its link_id: the webhook’s payment_id names the payment, not the link. A link that is not yours — or, for a PSP, not one of your sub-merchants’ — reads as not found:
PSPs do not need X-Merchant-ID here: a sub-merchant’s link is found without it. A buyer may try more than once before a payment goes through. Two fields show the payments made through the link:
  • paid_payment_id: The payment_id of the payment that paid the link, or null until it is paid. Refund and reconcile by this ID — see Tracking a payment link.
  • payments: The payments made through the link, newest first — at most the 50 newest. Each entry carries:
On some accounts a link and its payment share one ID. There payments holds a single entry whose payment_id is link_id, from the moment the link is created, and paid_payment_id becomes that same ID once the buyer pays. Elsewhere each try is a payment of its own, and payments stays empty until the buyer first tries to pay. A link the buyer paid on their second try, with the rest of the response left out:

Response Fields

The response carries no amount for the link. Keep the amount from Create Payment Link, or read amount from List Payment Links.
  • link_id: The link’s ID. payment_id is the same value, kept for compatibility.
  • expiry_date: When the link stops accepting payment. For a deactivated link, the moment it was deactivated.
  • mop_type: The method the buyer paid with, in uppercase (UPI, CREDIT_CARD) — List gives the same value in lowercase. It is null until the link is paid, and can stay null after. payments gives the method of each payment.
  • buyer, product, invoice: As sent on create.
    • buyer.pan_number and buyer.dob are null unless they were collected from the buyer.
    • product.hs_code and product.hs_code_description are null: the link does not store them.
    • invoice.date and invoice.file are null unless they were added to the order later.
  • settlement: The settlement state recorded against the link. settlement_details stays null until the payment is part of a settlement; its settlement_id is what Get Settlement takes. When paid_payment_id differs from link_id, the money moved on that payment rather than on the link, and settlement does not follow it: reconcile by paid_payment_id.
  • status_message: Why the link failed or closed, when there is a reason to give; otherwise null.
  • created_at and the other timestamps are UTC with microseconds, e.g. 2026-09-14T09:30:15.123456Z.

Authorizations

X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Path Parameters

The link's link_id, as returned by Create Payment Link (PR followed by 10 digits). The payment_id Create Payment Link returns is the same value.

Example:

"PR4829301756"

Response

The payment link

success
boolean
required

Indicates if the request was successful

message
string
required

Response message

data
object
required

The link, and the payments made through it. The link's amount is not included: keep the one from the create response, or read it from List Payment Links.