Bank Account to Wallet webhooks notify you in real time when an external bank account sends funds to a Verto wallet. These events are fired across the full inbound payment lifecycle — from the moment funds arrive at Verto's banking partners through compliance screening to final credit or rejection.
This webhook is your primary mechanism for knowing when a client or wallet has been credited, and is the recommended approach over polling the payments API for status updates.
Each event payload includes the walletId and companyId so you can identify exactly which wallet and which client has been credited. Where sender information is available from the originating bank — including sender name, account number, and bank details — this is included in the payload, making it straightforward to reconcile inbound payments against expected transfers or underlying customer activity.
Event lifecycle
Requested — fired as soon as Verto's banking partner receives the inbound funds and the payment enters the system. At this point the payment is undergoing transaction screening and the funds have not yet been credited to the wallet, but have been allocated to it. You should not treat this as a confirmed credit.
Completed — fired when the payment clears compliance review and the funds are credited to the wallet. This is the primary event to act on — your system should use this to update wallet balances, notify clients, or trigger downstream flows such as FX conversion or payout initiation where in your internal systems.
Disputed — fired when an inbound payment is flagged for investigation by Verto's compliance team or the originating bank. The payment is placed on hold pending resolution. You may be contacted with an RFI if additional information is required.
Archived — fired when an inbound payment is rejected and funds are returned to the sender. This may occur due to a failed compliance check or a payment from a restricted sender. No funds will be credited to the wallet.