VirtualAccountEvent
with a unique id
. You can:
VirtualAccountEvent
includes detailed information about the deposit, source, status, and destination.
type
field in the virtual account event object.
Type | Description |
---|---|
funds_received | Bridge received funds via ACH or wire. |
payment_submitted | Bridge submitted the crypto payment. |
payment_processed | Payment confirmed on-chain. Final state. |
funds_scheduled | (ACH only) Incoming funds are in transit with estimated arrival date. |
in_review | Transaction is under manual review. |
refunded | Funds could not be delivered and were refunded to the sender. |
account_update | Virtual Account was updated (e.g. new destination address). |
deactivation | Virtual Account was deactivated. |
reactivation | Virtual Account was reactivated. |
microdeposit | Microdeposit verification detected. Funds are never onramped. |
deposit_id
field. This id is unique for each transaction that Bridge receives through this Virtual Account and can be used to link separate events to the same source transaction.Funds received
funds_received
event amount always matches the full amount that the customer sent before any fees are deducted. We also provide any source information we have about the sender of a deposit.payment_rail
- ach_push
or wire
. The payment rail on which the deposit was received. Different information is available for each of these payment rail types.description
- This field contains the sender-related information set by the sending bank according to the NACHA ACH file specifications;sender_routing_number
- The routing number of the entity that initiated this ACH transactionsender_name
- The name of the business or individual who initiated the ACH as provided through the ACH systemtrace_number
- The unique, a 15-digit number associated with each ACH transaction that is used for tracking and reconciling transactionsbank_routing_number
- The routing number of the bank which sent this wirebank_name
- The name of the bank which sent this wirebank_beneficiary_name
- The name the sender used for the beneficiary name of the wireoriginator_name
- The name of the senderoriginator_address
- The address of the senderimad
- A unique number given to each FedWire payment when using the Federal Reserve Bank Service which can be used to investigate and track wire transfers.Payment submitted
payment_submitted
event amount is the funds sent to the destination after all fees are taken out and includes a breakdown of the amount of each fee. Some information such as destination_tx_hash
may not be available immediately after the event is created but will be populated later when the transaction is confirmed on chain.For convenience, the source deposit information is included in this event as well if available.Payment processed
payment_processed
event amount is the funds sent to the destination after all fees are taken out and includes a breakdown of the amount of each fee. Thedestination_tx_hash
will always be populated for these events. This is final event in the onramp payment lifecycle and the best event to determine when a payment is fully complete.For convenience, the source deposit information is included in this event as well if available.Funds scheduled
In review
Refund events
deposit_id
. This may be omitted in cases where the refund occurred before a deposit completed. For example:Bank verification
microdeposit
event for each verification attempt. This event includes the amount, source bank details, and timestamp—so you can display them to the customer for verification if needed.Account update
account_update
event to track what changed. The account_updates
field in this event will contain a map of fields with their previous and updated values.