List Payment ID Transactions API

Environment: Sandbox

Retrieve a Payment ID account summary and transaction records as an array using type 2 and an external reference.

# List Payment ID Transactions API

Retrieve a Payment ID account summary and its transactions using the external reference supplied when creating the Payment ID and your Moolre account number. Send type 2 for this lookup. Transactions are returned as an array.

## Endpoint
- **Method**: POST
- **URL**: https://sandbox.moolre.com/open/transact/status

## Headers
| Header | Type | Required | Description |
| :--- | :--- | :--- | :--- |
| X-API-USER | string | Yes | Your Moolre username. |
| X-API-PUBKEY | string | Yes | Your Public API Key. |

## Request Body
| Parameter | Type | Required | Description |
| :--- | :--- | :--- | :--- |
| type | integer | Yes | Must be 2 to retrieve Payment ID transactions. |
| externalref | string | Yes | External reference used when creating the Payment ID. |
| accountnumber | string | Yes | Your Moolre Account Number. |

## Response (200 (Found) Found)
The Payment ID was found. The response includes its account summary and a transactions array.

```json
{
  "status": 1,
  "code": "AC01",
  "message": "Payment ID / Bank Account Found",
  "data": {
    "account": {
      "accountno": "0052030001001",
      "txcount": "1",
      "txvalue": "4.60"
    },
    "transactions": [
      {
        "txstatus": 1,
        "txtype": 1,
        "accountnumber": "100000100002",
        "payer": "9040013020315",
        "payee": "Zagey",
        "amount": "5.00",
        "value": "4.60",
        "fee": "0.40",
        "networkfee": "0.00",
        "transactionid": "51531630",
        "externalref": "ur12ef001",
        "thirdpartyref": "2625201512860000",
        "ts": "2026-09-09 14:20:41"
      }
    ],
    "go": null
  },
  "meta": {
    "requestid": "req_c68f4c66115c26725c796242",
    "notices": []
  }
}
```

## Response (200 (Not Found) Not Found)
The lookup completed successfully, but no matching Payment ID was found. The account is null and transactions is an empty array.

```json
{
  "status": 1,
  "code": "AC03",
  "message": "Payment ID / Bank Account Not Found",
  "data": {
    "account": null,
    "transactions": [],
    "go": null
  },
  "meta": {
    "requestid": "req_c68f4c66115c26725c796242",
    "notices": []
  }
}
```


## Fields every response can carry

These fields are additive: existing fields keep their names, order and types.

| Field | Meaning |
| :--- | :--- |
| error | On a failure: { code, message, fields: [{ field, code, message }] } listing every failing field. |
| meta | Always present, last in the object. meta.replayed is true only when the response is the stored answer to a repeated Idempotency-Key (absent otherwise). meta.requestid is the unique id of the request (also the X-Request-Id response header): quote it when you contact support. meta.notices is always an array, empty when there is nothing to report; each notice is { code, message, docs? }, for example that a deprecated way of sending credentials was used. See [Deprecations](https://docs.moolre.com/guides/deprecations). |

There is no outcome field. Decide the result from status, code and, on payment and transfer endpoints, data.txstatus (0 pending, 1 succeeded, 2 failed). These codes mean the result is unknown and may still succeed, so treat them as pending and check the status: PY01, PY02, TR01, TR02, TP11, TP18, APY10, APY16, ASL06, SYS500. Status 1 with TR08, OBGH01, OTGH01, OBNG01, GHQ03 or OM03 is final success; any other status 1 is an accepted, unfinished request.

Send X-Moolre-Http-Status: strict to receive real HTTP status codes (400, 401, 403, 404, 409, 422, 429, 5xx) instead of HTTP 200. See [Responses and request IDs](https://docs.moolre.com/guides/responses).

Back to the Moolre AI documentation index