Skip to main content
POST
/
api
/
v2.0
/
qris
/
issuer
/
mpm
/
inquiry-merchant
Inquiry Merchant
curl --request POST \
  --url https://sandbox-payment-b2b.singapay.id/api/v2.0/qris/issuer/mpm/inquiry-merchant \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-PARTNER-ID: <api-key>' \
  --data '
{
  "qr_data": "00020101021226620015ID.SINGAPAY.WWW0118936012070412260002..."
}
'
{
  "response_code": "SP000",
  "response_message": "Successful",
  "data": {
    "payload_format_indicator": "01",
    "point_of_initiation_method": "DYNAMIC",
    "merchant_information_26": {
      "global_unique_identifier": "ID.SINGAPAY.WWW",
      "merchant_pan": "1234567890123456",
      "merchant_id": "1234567890",
      "merchant_criteria": "UMI"
    },
    "merchant_information_51": {
      "global_unique_identifier": "ID.SINGAPAY.WWW",
      "merchant_id": "1234567890",
      "merchant_criteria": "UMI"
    },
    "mcc": "5812",
    "transaction_currency": "RUPIAH",
    "transaction_amount": "100000.00",
    "country_code": "ID",
    "merchant_name": "Toko ABC",
    "merchant_city": "Jakarta",
    "merchant_postal_code": "12345",
    "additional_data": {
      "reference_label": "REF1234567890",
      "terminal_label": "C01",
      "purpose_of_transaction": "B4U5bV"
    },
    "crc": "4535"
  }
}

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.

Body

application/json
​
qr_data
string
required

Raw QRIS MPM payload string to decode.

Maximum string length: 500
Example:

"00020101021226620015ID.SINGAPAY.WWW0118936012070412260002..."

Response

Success — data contains the decoded QRIS payload or vendor-resolved merchant metadata (QrisIssuerMpmDecodedMerchantData).

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

Decoded merchant information from MPM QR data or vendor resolution. Contains fields commonly found in tag 26 of QRIS payloads, as well as any additional metadata resolved from the issuer vendor.