AsyncAPI channel · Chargebee
· Chargebee Webhooks
payment_source
Payment source (card, bank account, etc.) events.
Channel address
payment_source
Operations
subscribe
receivePaymentSourceEvent
Messages
card_added
card_added
Content-Type:
card_deleted
card_deleted
Content-Type:
card_expired
card_expired
Content-Type:
card_expiry_reminder
card_expiry_reminder
Content-Type:
card_updated
card_updated
Content-Type:
payment_source_added
payment_source_added
Content-Type:
payment_source_deleted
payment_source_deleted
Content-Type:
payment_source_expired
payment_source_expired
Content-Type:
payment_source_expiring
payment_source_expiring
Content-Type:
payment_source_locally_deleted
payment_source_locally_deleted
Content-Type:
payment_source_updated
payment_source_updated
Content-Type:
virtual_bank_account_added
virtual_bank_account_added
Content-Type:
virtual_bank_account_deleted
virtual_bank_account_deleted
Content-Type:
virtual_bank_account_updated
virtual_bank_account_updated
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.