Skip to main content
POST
Inquiry Status

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

Account identifier (ULID) for which to perform the lookup.

Body

application/json
reference_number
string
required
Maximum string length: 64
Example:

"INV-20231130-001"

scope
enum<string>
required
Available options:
issuer,
acquirer
Example:

"issuer"

type
enum<string> | null

Deprecated/unused — not required and not read by the endpoint.

Available options:
mpm-static,
mpm-dynamic,
cpm
Example:

"mpm-dynamic"

Response

Success — transaction found. data contains the transaction snapshot (QrisMoneyOutTransactionData).

API response envelope for successful QRIS money-out status inquiries. Conforms to the standard MerchantV2ApiEnvelope structure, with data containing a QrisMoneyOutTransactionData object representing the current state of the transaction.

response_code
string

Response code (see Response Code appendix) indicating the result of the inquiry. For successful inquiries, this is typically a code such as "00" or "SP000".

Example:

"SP000"

response_message
string

Human-readable message providing additional context about the response.

Example:

"Successful"

data
object

Inquiry status response data structure. Similar to QrisMoneyOutTransactionData but may be extended with additional fields relevant to status checks.