Skip to main content
PayVessel sends webhooks when virtual cards are created, used at merchants, funded, withdrawn, or terminated. Configure your webhook URL in the PayVessel Dashboard and verify every payload before updating balances or order status in your system. See Verifying Webhooks for signature checks, trusted IPs, and idempotent handling. These are example webhook responses for virtual card issuing.
Match cards using reference from create (lifecycle events) or card_id in the payload (transaction and termination events). Store PayVessel card_id from the API for your own lookups.

Transaction types

These are the possible transaction types on issuing.transaction:
  • AUTHORIZATION: When a card is successfully used at a merchant site.
  • SETTLEMENT: When a card is successfully used and settlement is completed at a merchant site.
  • FUNDING: When the card is funded via Fund a Card or create-time prefund.
  • WITHDRAWAL: When funds are withdrawn from the card via Withdraw from Card.
  • TERMINATION: When a card is terminated (also available from the PayVessel Dashboard).
  • DECLINE: When an attempt to use the card at a merchant site is rejected (for example insufficient balance).
  • REVERSAL: When a merchant charges a card but immediately returns that amount to the card.
  • REFUND: When a reversal does not complete as expected and funds erroneously debited are returned.
  • CROSS-BORDER: Cross-border use at merchants outside the US or when authorization currency is not USD.
mode can only be CREDIT or DEBIT.

What to do on each event

List transactions

Query normalized transaction history from the API