> ## Documentation Index
> Fetch the complete documentation index at: https://docs.singapay.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Movement Webhook

> Real-time notification when a balance transfer between two of your accounts finishes processing.

> [!NOTE]
>
> **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

| Method | Path | Format | Authentication |
| - | - | - | - |
| POST | `https://your-webhook-url/callback` | json | HMAC SHA512 Signature |

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

| Field | Value | Type | Mandatory | Description |
| - | - | - | - | - |
| `Content-Type` | `application/json` | Alphabetic | Yes | Specifies JSON format for the request body |
| `User-Agent` | `SingaPaymentGateway/1.0` | Alphabetic | Yes | Identifies the source of the webhook |
| `Accept` | `application/json` | Alphabetic | Yes | Expected response format |
| `X-PARTNER-ID` | — | Alphanumeric | Yes | Your API Key from the merchant dashboard |
| `X-Signature` | — | Alphanumeric | Yes | HMAC SHA512 signature (128 chars) for request verification |
| `X-Timestamp` | — | Numeric | Yes | Unix timestamp in **seconds** when the request was sent |
| `Authorization` | `Bearer <random_token>` | Alphanumeric | Yes | System-generated random bearer token; used as a component in the signature |

> [!NOTE]
>
> 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](https://docs.singapay.id/api-reference/webhooks/security-and-signature.md).

***

### Body Parameters

**status** `number` *required*

HTTP Status Code. Always `200`.

**success** `boolean` *required*

Indicates a successful event. Always `true`.

**event** `string` *required*

Event type identifier. Always `"movement-between-account.processed"`.

**timestamp** `string` *required*

Event timestamp in format `"d M Y H:i:s"`. Example: `"23 Sep 2026 11:32:41"`

**data** `object` *required*

**data fields**

**transaction\_id** `string` *required*

Unique identifier for this transfer.

**merchant\_ref\_no** `string`

Your reference number for this transfer, if one was supplied when it was created. May be `null`.

**amount** `number` *required*

Transfer amount in IDR. Example: `50000`

**remitter\_account\_id** `string`

Internal ID of the account the balance moved **from**. `null` when the remitter is a linked KYC e-money pool rather than one of your PG accounts (a KYC → PG transfer).

**remitter\_account\_name** `string`

Display name of the remitter account. `null` under the same condition as `remitter_account_id`.

**beneficiary\_account\_id** `string`

Internal ID of the account the balance moved **to**. `null` when the beneficiary is a linked KYC e-money pool rather than one of your PG accounts (a PG → KYC transfer).

**beneficiary\_account\_name** `string`

Display name of the beneficiary account. `null` under the same condition as `beneficiary_account_id`.

**source** `string` *required*

What initiated the transfer. One of `"Web"` (dashboard), `"API"`, or `"KYC"` (a linked KYC account moving funds into/out of your PG account).

**processed\_at** `string`

Timestamp the transfer finished processing, format `"d M Y H:i:s"`. `null` if unset.

> [!NOTE]
>
> `remitter_account_id`/`beneficiary_account_id` here are **internal account IDs**, not the account ULID (`id`) returned by [`GET /accounts/{id}`](https://docs.singapay.id/api-reference). 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

```json movement-between-account.processed theme={null}
{
  "status": 200,
  "success": true,
  "event": "movement-between-account.processed",
  "timestamp": "23 Sep 2026 11:32:41",
  "data": {
    "transaction_id": "TRX20260923113241001",
    "merchant_ref_no": "internal-transfer-882",
    "amount": 50000,
    "remitter_account_id": "142",
    "remitter_account_name": "SingaPay Demo Store - Main",
    "beneficiary_account_id": "217",
    "beneficiary_account_name": "SingaPay Demo Store - Reserve",
    "source": "Web",
    "processed_at": "23 Sep 2026 11:32:41"
  }
}
```

***

## Security and responses

Return HTTP `200` promptly after validating the request. For retry behavior, see [Webhook retry mechanism](https://docs.singapay.id/api-reference/webhooks/retry-mechanism.md).

Verify every webhook using [Security and signature validation](https://docs.singapay.id/api-reference/webhooks/security-and-signature.md). Use your configured `another_account_notif_url` path when building `StringToSign`.

Handle duplicate deliveries idempotently using `data.transaction_id`.

***

## Account Movement Specific Notes

> [accordion] Dedicated callback URL
>
> `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.

> [accordion] Sent to both sides of the transfer
>
> 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.

> [accordion] Null account fields on KYC-linked transfers
>
> 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.

> [accordion] Timestamp format & timezone
>
> `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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.