IBAN state change
Sent each time an IBAN allocated to a managed account is issued or changes state.
Allocation is asynchronous: a REQUESTED event is followed by CREATED once the IBAN can receive funds, or REJECTED if it could not be allocated.
Enable and configure webhooks in the Embedder Portal; recent events are listed on its Webhook Logs page. Weavr sends this event to {Webhook URL}/ibans/watch.
Headers
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
The timestamp, expressed in Epoch timestamp using millisecond precision, when this event was published.
The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the published-timestamp using your API key.
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
Example payload
{
"iban": {
"id": "123456789",
"managedAccountId": "123456789",
"profileId": "10001",
"incomingWireTransferProfileId": "10001",
"tag": "customer-123",
"friendlyName": "Main GBP account",
"currency": "GBP",
"creationTimestamp": 1786118400000,
"bankAccountDetails": [
{
"beneficiaryNameAndSurname": "Alex Smith",
"beneficiaryBank": "National Westminster Bank PLC",
"beneficiaryBankAddress": "250 Bishopsgate, London EC2M 4AA",
"paymentReference": "Invoice 1042",
"details": {
"iban": "GB29NWBK60161331926819",
"bankIdentifierCode": "NWBKGB2L"
}
}
]
},
"publishedTimestamp": 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.