Charge
Pulls funds from a bound bank account into the merchant settlement account.
Authorizations
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. Signature mismatch returns 401 with response_code=4019900.
Body
Pulls funds from an active binding into the merchant settlement account identified by account_id. The binding must be ACTIVE. merchant_reference is an idempotency key; replaying the same value returns 409 SP004 with the original transaction_id in data.
Response
SP000 Successfully. data matches DirectDebitTransactionData with status=PENDING (await settlement webhook) or status=SUCCESS on synchronous approval. fees are present only on SUCCESS.
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.
