Skip to main content
GET
/
api
/
v2.0
/
direct-debit
/
transactions
/
{transaction_id}
Get Transaction
curl --request GET \
  --url https://sandbox-payment-b2b.singapay.id/api/v2.0/direct-debit/transactions/{transaction_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'X-PARTNER-ID: <api-key>'
{
  "response_code": "SP000",
  "response_message": "OK",
  "data": {
    "transaction_id": "7c2e1a4b-9d6f-4e3a-8b1c-2d4f9a1c5b3e",
    "binding_id": "9a1c5b3e-2d4f-4d8c-93cf-9a1c5b3e2d4f",
    "account_id": "01HZX9JK4M5N6P7Q8R9STUVWXY",
    "merchant_reference": "INV-2026-0001",
    "amount": 150000,
    "currency": "IDR",
    "description": "Subscription June 2026",
    "status": "SUCCESS",
    "requires_otp": false,
    "paid_at": "2026-06-04T08:30:42+07:00",
    "failure_code": null,
    "failure_reason": null,
    "web_redirect_url": null,
    "created_at": "2026-06-04T08:30:01+07:00",
    "updated_at": "2026-06-04T08:30:43+07:00",
    "fees": {
      "vendor_fee": 1500,
      "platform_fee": 500,
      "merchant_fee": 2000,
      "total_fee": 2000,
      "net_amount": 148000
    }
  }
}

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

​
transaction_id
string<uuid>
required

UUID of a DirectDebitTransaction owned by the authenticated merchant.

Response

SP000 OK — data matches DirectDebitTransactionData. fees is populated only when status=SUCCESS; absent (not zero) on PENDING, PENDING_OTP, FAILED, and EXPIRED.

SingaPay Merchant API v2 custom response envelope (ApiResponderHelper::responseJson, ApiResponseTrait). Business outcome is determined by response_code (SP000–SP020), not by HTTP status alone. On success (SP000), data holds the operation payload. On errors, data often includes a message and may echo request fields.

​
response_code
string
required

SingaPay custom business response code.

Example:

"SP000"

​
response_message
string
required

Human-readable label paired with response_code.

Example:

"Successfully"

​
data
object | null

Endpoint-specific payload on success, or error context (validation message, inquiry result with status invalid, etc.).