Skip to main content
GET
/
api
/
v1.0
/
payment-link-histories
/
{account_id}
/
{history_id}
Show
curl --request GET \
  --url https://sandbox-payment-b2b.singapay.id/api/v1.0/payment-link-histories/{account_id}/{history_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'X-PARTNER-ID: <api-key>'
{
  "status": 200,
  "success": true,
  "data": {
    "id": 85,
    "reff_no": "12917720251024134439474",
    "payment_link_reff_no": "PL-20251024-0001",
    "payment_method_name": "VA BRI",
    "payment_method_value": "5588867273870397",
    "payment_method_additional": "a.n. SINGA PAYMENT",
    "expired_at": "2025-10-25T13:44:39+07:00",
    "amount": "1200000.00",
    "payment_date": "2025-10-24T13:45:07+07:00",
    "balance_after": "2500000.00",
    "status": "paid",
    "status_computed": "paid",
    "is_expired": true,
    "customer_name": "",
    "customer_email": "",
    "customer_phone": "",
    "ip_address": "103.133.68.7, 103.133.68.7",
    "locations": {},
    "processed_timestamp": "2025-10-24T13:45:07+07:00",
    "has_settle": true,
    "settle_at": "2025-10-24T15:00:00+07:00",
    "optional_metadata": {},
    "created_at": "2025-10-24T13:44:39+07:00",
    "updated_at": "2025-10-29T11:12:17+07:00"
  }
}

Authorizations

​
Authorization
string
header
required

JWT issued by POST /api/v1.1/access-token/b2b. Send Authorization: Bearer <token>.

​
X-PARTNER-ID
string
header
required

Merchant API key (Credential.api_key). Required on every request.

Path Parameters

​
account_id
string
required

ULID of the account that owns the payment link history. Must belong to the authenticated merchant.

Example:

"01HZX9K3P2J4M6N8Q0R2T4V6W8"

​
history_id
integer
required

Numeric id of the payment history record (payment_link_histories.id), as returned in the list endpoint id field.

Example:

85

Response

Success

Success envelope returned by the payment link history detail endpoint. Wraps a single history record in data.

​
status
integer
required

HTTP status code of the response.

Example:

200

​
success
boolean
required

Indicates whether the request was processed successfully. Always true for a 200 response.

Example:

true

​
data
object
required

The payment link history record.