---
title: "Get Transaction Status"
method: GET
path: "/gl/v1/payments/{id}/status"
tags: ["Payment"]
---

# Get Transaction Status

`GET /gl/v1/payments/{id}/status`

Returns the current lifecycle status of a payment. **Recommended after every GPI**
(PayDirect or PayCollect), even though PayGlocal also posts updates to
`merchantCallbackURL` — use status polling for reconciliation and as a fallback
if the callback is delayed or missed.

Call `GET /gl/v1/payments/{id}/status` with the PayGlocal `gid`, or use the
pre-signed `statusUrl` from the initiate response (`data.statusUrl`).

## Path parameters

- `id` string, required

## Response `200`

Status retrieved successfully. Top-level `status` reflects the transaction state;
`data` includes method-specific fields keyed by `payment-method`.

- ApiResponseTransactionStatus — Response envelope for `GET /gl/v1/payments/{id}/status`.
  - `gid` string — PayGlocal transaction ID.
  - `status` string — High-level transaction status (e.g. `SENT_FOR_CAPTURE`, `AUTHORIZED`, `INPROGRESS`).
  - `message` string — Human-readable status message.
  - `timestamp` string — Response timestamp (`DD/MM/YYYY HH:MM:SS`).
  - `reasonCode` string — Reason code for this status (e.g. `GL-201-001`).
  - `data` TransactionStatusData — `data` payload for transaction status. Fields present depend on `payment-method` (e.g. `CARD`, `UPI_INTENT`, `INB`, `ZIP`). See response examples on [Get Transaction Status](/api-reference/payments-v2/common/get-transaction-status).
    - `transactionCreationTime` string — Transaction creation time (`DD/MM/YYYY HH:MM:SS`).
    - `gid` string — PayGlocal transaction ID (may differ from top-level `gid` prefix).
    - `payment-method` string — Payment method code — `CARD`, `UPI_INTENT`, `INB`, `ZIP`, etc.
    - `Amount` string — Transaction amount.
    - `txnCurrency` string — ISO 4217 currency from the original payment request.
    - `merchantTxnId` string — Merchant transaction reference from initiate.
    - `merchantLogo` string, nullable — Merchant logo URL when configured (often `null`).
    - `detailedMessage` string — Processor or gateway detail message.
    - `Currency` string — Settlement or display currency.
    - `reasonCode` string — Status reason code (e.g. `GL-201-001`).
    - `status` string — Transaction lifecycle status inside `data` (e.g. `SENT_FOR_CAPTURE`, `AUTHORIZED`).
    - `CardBrand` string — Card network (`CARD` / Apple Pay). e.g. `VISA`.
    - `CardType` string — CREDIT or DEBIT (CARD only).
    - `Country` string — Card-issuing country (`CARD` only).
    - `processor` string — Processing rail (e.g. `payglocal`) for card payments.
    - `authApprovalCode` string — Issuer approval code (`CARD` only).
    - `upiTxnAmount` string — UPI transaction amount (`UPI_INTENT` only).
    - `upiTxnCurrency` string — UPI currency (`UPI_INTENT` only).
  - `errors` object, nullable — `null` on success.

## Other responses

- `401` — Authentication failed — invalid API key or digest.
- `404` — The specified onboardingId does not exist.

---

[API](https://skmtc.net/payglocal/apis/payglocal-api.md) · [All operations](https://skmtc.net/payglocal/apis/payglocal-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/payglocal/payglocal-api/revisions/498446abc56d/schema)