Trigger Payment Credit
Initiates an issuer-side MPM payment (money-out) from the merchant account. The endpoint creates a pending QrisTransaction, performs ledger debit and statement entries, and enqueues the vendor dispatch job (for supported vendors such as ALTO). See Response Code for the full SP000–SP020 reference; final settlement is performed asynchronously. CRITICAL: This is a money-out operation requiring X-Signature and X-Timestamp authentication per internal signing protocol.
Authorizations
JWT issued by POST /api/v1.1/access-token/b2b. Send Authorization: Bearer <token>.
Merchant API key (Credential.api_key). Required on every request.
Headers
HMAC-SHA512 hex signature, computed as HMAC_SHA512(clientSecret, "{HTTP_METHOD}:{REQUEST_URI}:{ACCESS_TOKEN}:{SHA256_HEX(MINIFIED_BODY)}:{X_TIMESTAMP}"). MINIFIED_BODY is the request body with object keys recursively sorted alphabetically and re-serialised with no whitespace (an empty/missing body hashes the empty string). ACCESS_TOKEN is the bearer token without the Bearer prefix. Missing header returns 422 (response_code=SP018); signature mismatch or unknown X-PARTNER-ID returns 401 (response_code=SP016).
ISO-8601 timestamp of the request; used as part of the signed string. Missing header returns 422 (response_code=SP018).
Body
Merchant idempotency key per account.
64"INV-20231130-001"
Account ULID.
99"01K946KF851RK7FX075GJHBVKF"
Net amount to beneficiary side (IDR).
1000 <= x <= 10000000100000
500"00020101021226620015ID.SINGAPAY.WWW0118936012070412260002..."
100"John Doe"
100"john.doe@example.com"
50"081234567890"
100"Jakarta"
Response
Request accepted. Transaction created and processing started asynchronously. data contains a QrisMoneyOutTransactionData snapshot (commonly status 03 — Pending).
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 (see Response Code appendix) indicating the result of the inquiry. For successful inquiries, this is typically a code such as "00" or "SP000".
"SP000"
Human-readable message providing additional context about the response.
"Successful"
Inquiry status response data structure. Similar to QrisMoneyOutTransactionData but may be extended with additional fields relevant to status checks.
