Managed accounts

Incoming wire transfer received

Sent when an incoming wire transfer is received into a managed account.

A deposit is normally reported twice: once as PENDING while it is being processed, and again as COMPLETED when the funds are credited. Reconcile on transactionId, and treat transactionFee as already deducted from the credited amount.

Sender details vary by payment network: senderIban is populated for SEPA and SWIFT, while senderSortCode and senderAccountNumber are populated for Faster Payments, BACS, and CHAPS.

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

postWebhook/managed_accounts/deposits/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.

transactionTimestampinteger required

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

state'PENDING' | 'COMPLETED' | 'REJECTED'

Where the deposit has reached:

  • PENDING: the deposit is being processed and funds are not yet available.
  • COMPLETED: the funds have been credited to the managed account. This is a final state.
  • REJECTED: the deposit was rejected and no funds were credited. This is a final state.
paymentNetwork'SEPA' | 'FASTER_PAYMENTS' | 'SWIFT' | 'BACS' | 'CHAPS' | 'RIX' | 'TARGET'
emailAddressstring

Email address of the user who effected the incoming wire transfer.

senderNamestring

Name of the sender, as supplied by the sending bank.

senderIbanstring

IBAN the funds were sent from. Present for SEPA and SWIFT transfers.

senderSortCodestring

Sort code the funds were sent from. Present for Faster Payments, BACS, and CHAPS transfers.

senderAccountNumberstring

Account number the funds were sent from. Present for Faster Payments, BACS, and CHAPS transfers.

senderAccountDescriptorstring

Free-form description of the sender's account, where the sending bank supplies one instead of structured details.

senderReferencestring

A reference supplied by the sender when creating the payment.

Example payload

{
  "id": {
    "id": "123456789",
    "type": "managed_accounts"
  },
  "owner": {
    "type": "example",
    "id": "123456789"
  },
  "transactionId": "123456789",
  "transactionAmount": {
    "currency": "GBP",
    "amount": 1250
  },
  "transactionFee": {
    "currency": "GBP",
    "amount": 1250
  },
  "transactionTimestamp": 1786118400000,
  "emailAddress": "alex.smith@example.com",
  "senderName": "Acme Ltd",
  "senderIban": "MT48MALT011000012345MTLCAST001S",
  "senderSortCode": "123456",
  "senderAccountNumber": "31926819",
  "senderReference": "Invoice 1042"
}

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.