AsyncAPI channel · Chargebee · Chargebee Webhooks

payment

Payment, refund, and payment intent events.

Open source AsyncAPI → All Chargebee channels Chargebee provider profile
Provider: Chargebee AsyncAPI: v2.6.0 Spec: Chargebee Webhooks Operations: 1 Messages: 10

Channel address

payment

Operations

receivePaymentEvent

Messages

authorization_succeeded
authorization_succeeded
Content-Type:
authorization_voided
authorization_voided
Content-Type:
payment_due_reminder
payment_due_reminder
Content-Type:
payment_failed
A payment attempt failed.
Content-Type:
payment_initiated
payment_initiated
Content-Type:
payment_intent_created
payment_intent_created
Content-Type:
payment_intent_updated
payment_intent_updated
Content-Type:
payment_refunded
payment_refunded
Content-Type:
payment_succeeded
A payment attempt succeeded.
Content-Type:
refund_initiated
refund_initiated
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.