Skip to main content
GET
/
v1
/
transactions
/
{id}
Get transaction by ID
curl --request GET \
  --url https://api.sbx.moduluslabs.io/reports/v1/transactions/{id} \
  --header 'X-API-Key: <api-key>'
{
  "data": {
    "id": "<string>",
    "amount": 123,
    "currency": "PHP",
    "created_at": "2023-11-07T05:31:56Z",
    "updated_at": "2023-11-07T05:31:56Z",
    "card_brand": "<string>",
    "card_last_four": "<string>",
    "correlation_id": "<string>",
    "amount_details": {
      "amount_authorized": 123,
      "amount_capturable": 123,
      "amount_received": 123,
      "amount_refunded": 123,
      "original_amount": 123,
      "tax_amount": 123,
      "final_amount": 123
    },
    "receipt": {
      "receipt_number": "<string>",
      "auth_number": "<string>",
      "batch_number": "<string>",
      "approval_code": "<string>",
      "reference_number": "<string>"
    },
    "merchant_details": {
      "merchant_name": "<string>",
      "merchant_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "partner_name": "<string>",
      "branch_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "branch_name": "<string>"
    },
    "terminal_details": {
      "terminal_name": "<string>",
      "activation_code": "<string>",
      "serial_number": "<string>"
    },
    "partner_name": "<string>",
    "activation_code": "<string>",
    "approval_code": "<string>",
    "reference_number": "<string>",
    "settlement_status": "<string>",
    "settled_at": "2023-11-07T05:31:56Z",
    "events": [
      {
        "event_type": "<string>",
        "created_at": "2023-11-07T05:31:56Z",
        "amount": "<string>",
        "description": "<string>",
        "reason": "<string>"
      }
    ]
  }
}
Returns the full transaction detail including amount_details, merchant_details, terminal_details, lifecycle events, and settlement information.

​
Transaction IDs

Transaction IDs vary by payment method:
Payment MethodID FormatExample
QRTransNumberTN-001
Card-PresentUUID550e8400-e29b-41d4-a716-446655440000
The API automatically detects the ID format and retrieves the transaction from the correct source.

​
Response Detail

The detail response includes fields not present in the list endpoint:
  • events — lifecycle events (authorization, capture, refund, etc.) with timestamps
  • approval_code — processor approval code
  • reference_number — external reference number
  • activation_code — terminal device identifier

​
Next Steps

List Transactions

Browse and filter transactions

List Branches

Get branch UUIDs for filtering

Authorizations

​
X-API-Key
string
header
required

API key for authentication. Verified by APISIX via Vanguard. APISIX injects identity headers and strips the raw key before forwarding.

Path Parameters

​
id
string
required

Transaction ID

Response

Transaction found

​
data
object
required