Virtual Account Assigned

This template is triggered when a virtual account has been assigned to the customer in an asynchronous flow.

Unlike in the synchronous assignment of virtual accounts, which are returned in the response of the respective APIs, clients do not receive certain virtual accounts immediately in the response of the APIs. This happens in cases of an asynchronous assignment of virtual accounts. In the latter case, the webhook introduced notifies the clients once the virtual accounts have been assigned.




Request example

curl --location --request POST 'https://<customerHost:Port>/webhook' \
-H 'content-type: application/json' \
-d '{
       "fullBankName":"JPMorgan Chase Bank N.A., London",
       "accountName":"NIUM FINTECH LIMITED",
       "bankAddress":"25 Bank Street Canary Wharf, London, E14 5JP, United Kingdom",

Request body

clientHashIdThe unique client identifier generated and shared before API handshake.UUID
customerHashIdThe unique customer identifier generated on customer creation.UUID
walletHashIdThe unique wallet identifier generated simultaneously with customer creation.UUID
currencyCodeThe three-letter ISO-4217 currency code.String
uniquePaymentIdThe unique payment ID.String
uniquePayerIdThe unique payer ID.String
fullBankNameThe complete name of the bank for the virtual account.String
routingCodeType1The first routing code type. See the Examples of Routing Codes.String
routingCodeValue1The routing code value for routingCodeType1String
routingCodeType2The second routing code type. See the Examples of Routing Codes.String
routingCodeValue2The routing code value for routingCodeType2String
accountNameThe account name to be mentioned while doing a fund transfer.String
accountTypeThe account type. The possible values are:
bankAddressThe bank address.String
templateThe value for this field is VIRTUAL_ACCOUNT_ASSIGNED_WEBHOOK.String