Check Order Status

Retrieves the current status and details of a payment order

GET /api/products/payments/:orderId

cURL

curl -X GET https://juadah-backend.vercel.app/api/products/payments/66e4fa55-fdac-4ef9-91b5-733b97d1b862 \
  -H "Cookie: accessToken=your_access_token"

200 - Success (Completed Order)

{
  "status": "success",
  "data": {
    "order_id": "66e4fa55-fdac-4ef9-91b5-733b97d1b862",
    "transaction_id": "d4e86f7c-3e4d-4f5e-8c3b-9a2b1c0d8e7f",
    "transaction_status": "settlement",
    "product_id": 1,
    "product_name": "Kue Bolu",
    "total_price": "50000",
    "completed_at": 1709456789000,
    "created_at": 1709456123000
  }
}

Overview

This endpoint allows you to check the status of a payment order using its order ID. It returns comprehensive information about the order including transaction status, product details, and timestamps.

Authentication

This endpoint requires authentication via cookie-based access token.

Path Parameters

orderId · string · required

The unique order ID (UUID format) returned when the order was created

Response

status · string

Response status, always “success” for successful requests

data · object

Order status details

Show properties

order_id · string

The unique identifier for the order (UUID)

transaction_id · string

The transaction ID from the payment provider (Midtrans)

transaction_status · string

Current status of the transaction. Possible values:

• pending - Payment is awaiting completion
• capture - Payment has been captured (credit card)
• settlement - Payment has been settled
• deny - Payment was denied
• cancel - Payment was cancelled
• expire - Payment expired
• failure - Payment failed
• refund - Payment was refunded
• partial_refund - Payment was partially refunded
• authorize - Payment is authorized but not captured

product_id · integer

The ID of the product that was ordered

product_name · string

The name of the product

total_price · string

The total price of the order (as a string to preserve precision)

completed_at · integer

Unix timestamp (in milliseconds) when the order was completed. null if not yet completed

created_at · integer

Unix timestamp (in milliseconds) when the order was created

cURL

curl -X GET https://juadah-backend.vercel.app/api/products/payments/66e4fa55-fdac-4ef9-91b5-733b97d1b862 \
  -H "Cookie: accessToken=your_access_token"

200 - Success (Completed Order)

{
  "status": "success",
  "data": {
    "order_id": "66e4fa55-fdac-4ef9-91b5-733b97d1b862",
    "transaction_id": "d4e86f7c-3e4d-4f5e-8c3b-9a2b1c0d8e7f",
    "transaction_status": "settlement",
    "product_id": 1,
    "product_name": "Kue Bolu",
    "total_price": "50000",
    "completed_at": 1709456789000,
    "created_at": 1709456123000
  }
}

Notes

• The order_id must be a valid UUID that was returned from the “Request Order Token” endpoint
• The completed_at field is only populated when transaction_status is settlement or capture
• Timestamps are in milliseconds since Unix epoch
• The total_price is returned as a string to preserve decimal precision
• This endpoint can be polled to check for payment completion after redirecting the customer to Midtrans