Skip to main content
Bridge now supports webhook events for the following categories:
  • customer
  • kyc_link
  • liquidation_address.drain
  • static_memo.activity
  • transfer
  • virtual_account.activity
  • bridge_wallet.activity
  • card_account
  • card_transaction
  • posted_card_account_transaction
  • card_withdrawal
  • external_acccount
  • rfi (beta)
Additional event categories will be added soon.

💬 Feedback welcome — Let us know which event types you’d like to see prioritized next.

Supported Event Types

Event Object Schema

Each webhook payload includes:

Event Object Schema Reference

The event_object field contains the full resource data, matching the structure returned by corresponding API endpoints. Webhooks and API responses use identical rendering logic, ensuring schema consistency.

Supported Mutation Types

Each event can have the following mutation types:
  • created
  • updated
  • updated.status_transitioned (for state transitions like KYC or Transfer status)
  • deleted (if applicable)

Examples

Transfers

First event for a transfer: created, waiting on the customer’s deposit.

Liquidation Address Drains

A liquidation address drain moves funds out of a liquidation address and follows the same lifecycle as a transfer, from initial receipt through to final settlement or return.
A deposit was detected at the liquidation address and a drain record was created.

Card Accounts

status is one of active, pending, inactive, frozen (frozen can override any of the other three while a freeze is in effect). card_details, balances, cardholder_name, and funding instructions are only included once the account has finished provisioning and has at least one card issued against it — they are omitted for an account that hasn’t finished provisioning yet, or that was closed before any cards were issued.
Card account created; still provisioning with the issuing vendor.

Card Transactions

Fires as a card transaction moves through authorization, capture, and settlement. status is one of approved, denied, expired, settled, merchant_credit_on_hold, incrementally_settled, reversed, partially_reversed, incremental_auth_approved. category is one of purchase, refund, adjustment, fee.
Authorization approved, transaction still open.

Posted Card Account Transactions

Settled activity from the posted-transaction history feed. status is always posted — this category only ever fires created/updated, never updated.status_transitioned, since the public status does not change once posted. category is one of purchase, refund, adjustment, fee, crypto_funding, crypto_withdrawal, crypto_return.

Card Withdrawals

status is one of pending, in_review, in_progress, completed, failed. type is top_up_balance_withdrawal or fee.

Virtual Account Activity

type is one of funding, drain, microdeposit, account_update, refund_in_flight, refund, refund_failed, in_review, payment_processed, deactivation, activation, funds_scheduled, close.
An incoming fiat deposit was received and converted to the destination asset.

Static Memo Activity

Behaves the same as Virtual Account Activity, but the deposit product is a static memo rather than a dedicated bank account: the object carries static_memo_id instead of virtual_account_id, and the source side carries a source_deposit_instructions.deposit_message (the memo string) rather than bank-transfer source fields. Only the two most common cases are shown here — every type value from the Virtual Account Activity section above applies equally.

External Accounts

External bank account linked to a customer. For webhook rendering, address and account_owner_country are deliberately excluded (they are included in API responses but not webhooks).

Customers

A new customer record was created. KYC has not yet started.
A KYC link was generated and sent to the customer. Neither KYC nor ToS acceptance has started.