AsyncAPI channel · Paystack · Paystack Webhooks

paystack/events

The merchant's single webhook URL. Paystack POSTs every event type defined in this document to the same channel; consumers branch on the `event` field of the payload.

Provider: Paystack AsyncAPI: v2.6.0 Spec: Paystack Webhooks Operations: 1 Messages: 24

Channel address

paystack/events

Operations

publish
receivePaystackEvent
Receive a Paystack webhook event

Messages

ChargeSuccess
A successful transaction (charge) was completed.
Content-Type: application/json
ChargeDisputeCreate
A dispute was logged against your business.
Content-Type: application/json
ChargeDisputeRemind
A logged dispute has not yet been resolved.
Content-Type: application/json
ChargeDisputeResolve
A dispute has been resolved.
Content-Type: application/json
CustomerIdentificationSuccess
Customer identity validation succeeded.
Content-Type: application/json
CustomerIdentificationFailed
Customer identity validation failed.
Content-Type: application/json
DedicatedAccountAssignSuccess
A Dedicated Virtual Account was assigned to a customer.
Content-Type: application/json
DedicatedAccountAssignFailed
Dedicated Virtual Account assignment failed.
Content-Type: application/json
InvoiceCreate
A subscription invoice has been created.
Content-Type: application/json
InvoiceUpdate
A subscription invoice was updated (typically a successful charge).
Content-Type: application/json
InvoicePaymentFailed
A subscription invoice payment failed.
Content-Type: application/json
PaymentRequestSuccess
A payment request was paid.
Content-Type: application/json
PaymentRequestPending
A payment request has been sent to a customer.
Content-Type: application/json
RefundFailed
A refund could not be processed.
Content-Type: application/json
RefundPending
A refund was initiated and is awaiting processor response.
Content-Type: application/json
RefundProcessed
A refund has been successfully processed.
Content-Type: application/json
RefundProcessing
A refund has been received by the processor.
Content-Type: application/json
SubscriptionCreate
A subscription has been created.
Content-Type: application/json
SubscriptionDisable
A subscription has been disabled.
Content-Type: application/json
SubscriptionNotRenew
A subscription has been flagged as non-renewing.
Content-Type: application/json
SubscriptionExpiringCards
Monthly report of subscriptions whose cards are expiring.
Content-Type: application/json
TransferSuccess
A transfer has completed successfully.
Content-Type: application/json
TransferFailed
A transfer attempt failed.
Content-Type: application/json
TransferReversed
A transfer was reversed.
Content-Type: application/json

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 Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel
curl "https://apis.io/api/v1/channels/paystack-events"
All event channels
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.