Manage

Manual transaction

Sent when Weavr manually credits or debits an instrument, for example to correct a processing error or settle a dispute.

The available and actual balance adjustments are reported separately because they can differ: a correction may release a held amount without moving settled funds.

Enable and configure webhooks in the Embedder Portal; recent events are listed on its Webhook Logs page. Weavr sends this event to {Webhook URL}/manual_transactions/watch.

postWebhook/manual_transactions/watch

Headers

call-refstring

A call reference generated by the caller and unique to the caller to provide correlation between the caller and system with a maximum length of 255

published-timestampinteger required

The timestamp, expressed in Epoch timestamp using millisecond precision, when this event was published.

signaturestring required

The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the published-timestamp using your API key.

signature-v2string required

The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the call-ref + payload + published-timestamp using your API key.

Payload

transactionIdstring required

The unique identifier of the transaction, for reference.

availableBalanceAdjustmentinteger

The amount credited to or debited from the instrument's available balance, scaled to the lowest denomination of the instrument's currency.

actualBalanceAdjustmentinteger

The amount credited to or debited from the instrument's actual balance, scaled to the lowest denomination of the instrument's currency.

transactionTimestampinteger required

When the transaction was processed. Epoch timestamp using millisecond precision.

Example payload

{
  "transactionId": "123456789",
  "targetInstrument": {
    "id": "123456789",
    "type": "managed_accounts"
  },
  "owner": {
    "type": "example",
    "id": "123456789"
  },
  "availableBalanceAdjustment": 1250,
  "actualBalanceAdjustment": 1250,
  "transactionTimestamp": 1786118400000
}

Response

Event received.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.