Skip to main content
Dedicated, optional webhook — this fires for transfers made with the “move money between accounts” feature (balance moved from one of your accounts to another, including transfers into/out of a linked KYC e-money pool). It does not cover money-in/money-out transactions from your customers.

Information

SingaPay sends a POST request to your configured another_account_notif_url whenever an account-to-account transfer finishes processing, regardless of whether it was initiated from the dashboard, the API, or a linked KYC account. Only one event is emitted: movement-between-account.processed.

Who receives it

The webhook is sent separately to both sides of the transfer — the remitter’s resolved callback URL and the beneficiary’s resolved callback URL. Each side resolves to an account-specific another_account_notif_url if one is configured for that account, otherwise your merchant-level default. If both sides resolve to the same URL, you receive one call, not two.

Request Details

Headers

The Authorization token is a randomly generated string, not a user access token — account movement events are triggered by a completed transfer, not a merchant-initiated request that already carries one. Extract the token as-is and use it in the string to sign. See Security and signature validation.

Body Parameters

number
required
HTTP Status Code. Always 200.
boolean
required
Indicates a successful event. Always true.
string
required
Event type identifier. Always "movement-between-account.processed".
string
required
Event timestamp in format "d M Y H:i:s". Example: "23 Sep 2026 11:32:41"
object
required
remitter_account_id/beneficiary_account_id here are internal account IDs, not the account ULID (id) returned by GET /accounts/{id}. Match accounts by name, or by the ULID you already hold for accounts you manage, rather than expecting this field to line up with the API’s account id.

Payload Example

movement-between-account.processed

Security and responses

Return HTTP 200 promptly after validating the request. For retry behavior, see Webhook retry mechanism. Verify every webhook using Security and signature validation. Use your configured another_account_notif_url path when building StringToSign. Handle duplicate deliveries idempotently using data.transaction_id.

Account Movement Specific Notes

another_account_notif_url (labeled Account Movement Notif URL in the dashboard) is a dedicated, optional field — it does not share a callback URL with any other webhook type. Configure it under Settings → Credentials → Webhook & Notification URLs, either at the merchant level or per account.
Unlike most webhooks, this one can fire twice for a single transfer — once for the remitter’s callback URL, once for the beneficiary’s — if they resolve to different URLs. If your integration only cares about one side, filter on whether remitter_account_id or beneficiary_account_id matches an account you own a callback URL for.
When a transfer crosses into or out of a linked KYC e-money pool (source: "KYC", or a "Web"/"API" transfer targeting a KYC account), the PG-side account on that leg has no local account row — its _id and _name fields come through as null. Don’t treat a null remitter/beneficiary as a malformed payload.
timestamp and processed_at use the format "d M Y H:i:s" (e.g. "23 Sep 2026 11:32:41") in Asia/Jakarta (WIB) timezone — not UTC.