Transaction Query

Query the current status and full details of any transaction — whether created via Checkout, S2S Card, or iFrame.

Endpoint: POST /v2/checkout/query
Content-Type: application/json

---

Request

Field	Type	Required	Description
transactionId	String (ULID)	M	GLODIPAY transaction ID
signVersion	String	O	2.1: send the other fields as a JSON string in payload (see Signature). Omit to use the 2.0 rules.
signature	String(max:750)	M	RSA-MD5 signature. See Signature

Example request:

{
  "transactionId": "01jza90dy6w82dfrrqvadn5vs4"
}

With signVersion 2.1, these fields are sent as a JSON string in payload, alongside signVersion and signature. See Signature.

---

Response

Content-Type: application/json

Field	Type	Description
merchantId	String	Merchant's ID
transactionId	String	GLODIPAY transaction ID (ULID)
transactionNumber	String	GLODIPAY human-readable transaction number
ref	String	Merchant's orderRef
currency	String	ISO 4217 currency code
amount	Float	Invoice amount
paidAmount	Float	Amount actually charged to the buyer (including buyer fees)
settlementAmount	Float	Amount to be settled to the merchant
estimationSettlementAt	ISO 8601 datetime	Estimated settlement datetime
fees	JSON	Fee breakdown. See fees object
status	String	Transaction status. See Status Values
statusCode	Number	Numeric status code. See Status Codes
metadata	JSON	Key-value pairs from the original session
transactionDocuments	JSON	Supporting documents from the original session
paymentMethodDetails	JSON	Payment method used. See paymentMethodDetails object
message	String	Human-readable status message
descriptor	String	Transaction descriptor
transactionCreatedAt	ISO 8601 datetime	Transaction creation time in GLODIPAY system
originalTransactionCreatedAt	ISO 8601 datetime	Transaction creation time at the PSP
signature	String	2.0 only — on 2.1 the signature is sent next to payload. See Signature

Example response:

{
  "merchantId": "1100000123",
  "transactionId": "01jza90dy6w82dfrrqvadn5vs4",
  "transactionNumber": "2604-1713100800",
  "ref": "ORDER-001",
  "currency": "USD",
  "amount": 100.00,
  "paidAmount": 105.00,
  "settlementAmount": 95.00,
  "estimationSettlementAt": "2026-04-16T00:00:00+00:00",
  "fees": {
    "buyer": 5.00,
    "seller": 5.00,
    "rolling": 2.00,
    "operate": 3.00,
    "estimationRollingReleaseAt": "2026-05-14T00:00:00+00:00"
  },
  "status": "successful",
  "statusCode": 6,
  "paymentMethodDetails": {
    "displayName": "Credit / Debit Card",
    "group": "card",
    "family": "card",
    "type": "card",
    "card": {
      "name": "John Doe",
      "firstSixDigits": "411111",
      "lastFourDigits": "1111",
      "expiryMonth": "01",
      "expiryYear": "30",
      "type": "visa"
    }
  },
  "metadata": { "orderId": "12345" },
  "message": null,
  "descriptor": "GLODIPAY*ORDER-001",
  "transactionCreatedAt": "2026-04-14T10:00:00+00:00",
  "originalTransactionCreatedAt": "2026-04-14T10:00:01+00:00"
}

2.1 accounts receive these fields as a JSON string in payload, alongside signVersion and signature; 2.0 accounts receive them flat with signature. See Signature.

---

Notes

• The query response contains the same fields as the IPN notification payload. Use it to reconcile payment status when an IPN was not received.
• Always verify the signature in the query response before trusting the status.
• The transactionId is returned in the Checkout, S2S Card, and iFrame API responses when the session is created.