Skip to main content
GET
Get Payment

Overview

Returns the full record of one payment: the order it belongs to, the settlement that paid it out, any refunds against it, and details of the method the buyer used. Take the payment_id from List Payments or from a payment webhook.
PSPs can fetch any payment they can act for: their own, or any sub-merchant’s. X-Merchant-ID is not needed here, and does not narrow the lookup.

Payment status

status is the payment’s status as recorded: pending, captured or failed.
A pending payment that has expired still reads pending here. List Payments shows the same payment as failed. Treat a pending payment whose order has passed its expiry as failed.
order.status is the order’s status, not the payment’s: payment_pending, payment_successful or failed. An order can have several payments, one per attempt, so a failed payment can belong to a payment_successful order.

Response Fields

  • order.amount is a decimal string with two places, e.g. "1500.00". The same applies to settlement.settlement_amount and refund[].refund_amount. Parse them as decimals, never as floats.
  • settlement is null until the payment is settled.
  • refund lists refunds against the payment, newest first, and is [] when there are none. refund_status is one of initiated, processing, refunded, failed, reversed, on_hold or bank_rejected_refund.
  • collection_mode is how the payment was collected: hosted_payment, payment_link or s2s.
  • mop_type and order.opted_mop_type are lowercase, e.g. upi or credit_card. opted_mop_type is the method chosen when the order was created; mop_type is the one the buyer actually used.
  • mop_detail depends on mop_type:
Any field inside mop_detail can be null when the payment provider did not return it.
  • created_at, payment_completed_at, order.created_at, and the timestamps under settlement and refund, are UTC with microseconds, e.g. 2026-10-15T06:44:13.414209Z.

Errors

A payment ID that does not exist, or belongs to a merchant you cannot act for, returns 404:
The response is the same whatever X-API-Version you send. v1, v2 and v3 integrations share this endpoint and its response.

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

payment_id
string
required

Payment ID, e.g. PR4350279153.

Response

The payment

success
boolean
message
string
data
object