deposit_message !
For Static Memos, it is very important that the customer includes the deposit_message
when they send funds. Failure to include the deposit_message
will result in a significant delay in processing or a return of the funds.blockchain_memo
in the destination field. Bridge will forward the memo when sending crypto funds.
account_update
event in the history for that account.
Event | Description |
---|---|
funds_received | Bridge has received funds and is preparing to move them on the customer’s behalf. |
payment_submitted | Bridge has sent the payment and is awaiting confirmation (usually takes a few minutes on-chain). |
payment_processed | Funds have arrived at the destination. Final state. |
in_review | Temporary review state. Bridge may reach out for additional info. |
refund | Bridge couldn’t complete the transfer and is returning funds to the sender. |
account_update | Triggered when a Virtual Account’s destination details (e.g. address, currency) are updated. |
funds_received
→ payment_submitted
→ payment_processed
. It can never go backwards.
All transaction-triggered events include a deposit_id
field. This id is unique for each transaction that Bridge receives through this Static Memo 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. The information available differs by source payment rail: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 customer-facing fee. Some information such as destination_tx_hash
may not be available immediately after the payment_submitted
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.In review
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.