Paystack webhook events
35 Paystack event types in 6 resources, plus Other Paystack events. 33 have sample payloads.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
charge
charge.dispute.create
documented from Paystack docs (example)
charge.dispute.create Customer opens a dispute against your business
Identified by event field in the body
Resource charge
{
"event": "charge.dispute.create",
"data": { … }
} From Paystack docs
-
Content type
application/json
charge.dispute.remind
documented from Paystack docs (example)
charge.dispute.remind Open dispute still hasn't been resolved
Identified by event field in the body
Resource charge
{
"event": "charge.dispute.remind",
"data": { … }
} From Paystack docs
-
Content type
application/json
charge.dispute.resolve
documented from Paystack docs (example)
charge.dispute.resolve Dispute reaches a resolution
Identified by event field in the body
Resource charge
{
"event": "charge.dispute.resolve",
"data": { … }
} From Paystack docs
-
Content type
application/json
charge.failed
documented No payload yet
charge.failed Charge attempt fails
Identified by event field in the body
Resource charge
No payload yet.
charge.success
documented official schema
charge.success Charge completes successfully
Identified by event field in the body
Resource charge
{
"event": "charge.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
invoice
invoice.create
documented from Paystack docs (example)
invoice.create Subscription invoice is raised, usually three days before the charge
Identified by event field in the body
Resource invoice
{
"event": "invoice.create",
"data": { … }
} From Paystack docs
-
Content type
application/json
invoice.payment_failed
documented official schema
invoice.payment_failed Payment attempt on an invoice fails
Identified by event field in the body
Resource invoice
{
"event": "invoice.payment_failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
invoice.update
documented from Paystack docs (example)
invoice.update Invoice changes, usually after a successful charge
Identified by event field in the body
Resource invoice
{
"event": "invoice.update",
"data": { … }
} From Paystack docs
-
Content type
application/json
preauthorization
preauthorization.capture.failed
documented official schema
preauthorization.capture.failed Capturing a preauthorized amount fails
Identified by event field in the body
Resource preauthorization
{
"event": "preauthorization.capture.failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
preauthorization.capture.success
documented official schema
preauthorization.capture.success Preauthorized amount is captured
Identified by event field in the body
Resource preauthorization
{
"event": "preauthorization.capture.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
preauthorization.release.failed
documented official schema
preauthorization.release.failed Releasing a preauthorization hold fails
Identified by event field in the body
Resource preauthorization
{
"event": "preauthorization.release.failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
preauthorization.release.success
documented official schema
preauthorization.release.success Preauthorization hold is released
Identified by event field in the body
Resource preauthorization
{
"event": "preauthorization.release.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
preauthorization.reserve.success
documented from Paystack docs (example)
preauthorization.reserve.success Preauthorization hold is placed on a card
Identified by event field in the body
Resource preauthorization
{
"event": "preauthorization.reserve.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
refund
refund.failed
documented official schema
refund.failed Refund can't be processed, and the amount returns to your balance
Identified by event field in the body
Resource refund
{
"event": "refund.failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
refund.needs-attention
documented from Paystack docs (example)
refund.needs-attention Refund reaches the needs-attention status
Identified by event field in the body
Resource refund
{
"event": "refund.needs-attention",
"data": { … }
} From Paystack docs
-
Content type
application/json
refund.pending
documented official schema
refund.pending Refund starts and waits on the processor
Identified by event field in the body
Resource refund
{
"event": "refund.pending",
"data": { … }
} From Paystack docs
-
Content type
application/json
refund.processed
documented official schema
refund.processed Processor completes a refund
Identified by event field in the body
Resource refund
{
"event": "refund.processed",
"data": { … }
} From Paystack docs
-
Content type
application/json
refund.processing
documented official schema
refund.processing Processor receives a refund
Identified by event field in the body
Resource refund
{
"event": "refund.processing",
"data": { … }
} From Paystack docs
-
Content type
application/json
subscription
subscription.create
documented from Paystack docs (example)
subscription.create New subscription is created
Identified by event field in the body
Resource subscription
{
"event": "subscription.create",
"data": { … }
} From Paystack docs
-
Content type
application/json
subscription.disable
documented from Paystack docs (example)
subscription.disable Subscription is disabled
Identified by event field in the body
Resource subscription
{
"event": "subscription.disable",
"data": { … }
} From Paystack docs
-
Content type
application/json
subscription.expiring_cards
documented official schema
subscription.expiring_cards Monthly list of subscriptions whose cards expire that month
Identified by event field in the body
Resource subscription
{
"event": "subscription.expiring_cards",
"data": [ … ]
} From Paystack docs
-
Content type
application/json
subscription.not_renew
documented from Paystack docs (example)
subscription.not_renew Subscription turns non-renewing, so its next charge won't run
Identified by event field in the body
Resource subscription
{
"event": "subscription.not_renew",
"data": { … }
} From Paystack docs
-
Content type
application/json
transfer
transfer.failed
documented from Paystack docs (example)
transfer.failed Outgoing transfer fails
Identified by event field in the body
Resource transfer
{
"event": "transfer.failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
transfer.reversed
documented from Paystack docs (example)
transfer.reversed Outgoing transfer is reversed
Identified by event field in the body
Resource transfer
{
"event": "transfer.reversed",
"data": { … }
} From Paystack docs
-
Content type
application/json
transfer.success
documented official schema
transfer.success Outgoing transfer completes
Identified by event field in the body
Resource transfer
{
"event": "transfer.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
Other Paystack events
bank.transfer.rejected
documented from Paystack docs (example)
bank.transfer.rejected Customer's bank transfer is rejected, for example for a wrong amount
Identified by event field in the body
{
"event": "bank.transfer.rejected",
"data": { … }
} From Paystack docs
-
Content type
application/json
customeridentification.failed
documented from Paystack docs (example)
customeridentification.failed Customer identity validation fails
Identified by event field in the body
{
"event": "customeridentification.failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
customeridentification.success
documented from Paystack docs (example)
customeridentification.success Customer identity validation passes
Identified by event field in the body
{
"event": "customeridentification.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
dedicatedaccount.assign.failed
documented from Paystack docs (example)
dedicatedaccount.assign.failed Dedicated virtual account can't be assigned to a customer
Identified by event field in the body
{
"event": "dedicatedaccount.assign.failed",
"data": { … }
} From Paystack docs
-
Content type
application/json
dedicatedaccount.assign.success
documented from Paystack docs (example)
dedicatedaccount.assign.success Dedicated virtual account is assigned to a customer
Identified by event field in the body
{
"event": "dedicatedaccount.assign.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
direct_debit.authorization.active
documented official schema
direct_debit.authorization.active Direct debit authorization becomes chargeable
Identified by event field in the body
{
"event": "direct_debit.authorization.active",
"data": { … }
} From Paystack docs
-
Content type
application/json
direct_debit.authorization.created
documented official schema
direct_debit.authorization.created Customer approves a direct debit authorization request
Identified by event field in the body
{
"event": "direct_debit.authorization.created",
"status": true,
"message": "Authorization retrieved successfully",
"data": { … }
} Key fields
| Field | Type | Example |
|---|---|---|
status | boolean | true |
Full schema: 25 fields.
From Paystack docs
-
Content type
application/json
paymentrequest.pending
documented from Paystack docs (example)
paymentrequest.pending Payment request goes out to a customer
Identified by event field in the body
{
"event": "paymentrequest.pending",
"data": { … }
} From Paystack docs
-
Content type
application/json
paymentrequest.success
documented from Paystack docs (example)
paymentrequest.success Customer pays a payment request
Identified by event field in the body
{
"event": "paymentrequest.success",
"data": { … }
} From Paystack docs
-
Content type
application/json
zero_charge_authorization.failed
documented No payload yet
zero_charge_authorization.failed Zero-amount card authorization fails
Identified by event field in the body
No payload yet.
Route Paystack events by type.
Event Gateway receives every Paystack delivery and filters and routes it by event type, so each service gets only the events it handles.