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)

Customer opens a dispute against your business

Identified by event field in the body Resource charge

paystack-charge-dispute-create.json
{
  "event": "charge.dispute.create",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

charge.dispute.remind

documented from Paystack docs (example)

Open dispute still hasn't been resolved

Identified by event field in the body Resource charge

paystack-charge-dispute-remind.json
{
  "event": "charge.dispute.remind",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

charge.dispute.resolve

documented from Paystack docs (example)

Dispute reaches a resolution

Identified by event field in the body Resource charge

paystack-charge-dispute-resolve.json
{
  "event": "charge.dispute.resolve",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

charge.failed

documented No payload yet

Charge attempt fails

Identified by event field in the body Resource charge

No payload yet.

Help fill this in → View as JSON

charge.success

documented official schema

Charge completes successfully

Identified by event field in the body Resource charge

paystack-charge-success.json
{
  "event": "charge.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

invoice

invoice.create

documented from Paystack docs (example)

Subscription invoice is raised, usually three days before the charge

Identified by event field in the body Resource invoice

paystack-invoice-create.json
{
  "event": "invoice.create",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

invoice.payment_failed

documented official schema

Payment attempt on an invoice fails

Identified by event field in the body Resource invoice

paystack-invoice-payment-failed.json
{
  "event": "invoice.payment_failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

invoice.update

documented from Paystack docs (example)

Invoice changes, usually after a successful charge

Identified by event field in the body Resource invoice

paystack-invoice-update.json
{
  "event": "invoice.update",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

preauthorization

preauthorization.capture.failed

documented official schema

Capturing a preauthorized amount fails

Identified by event field in the body Resource preauthorization

paystack-preauthorization-capture-failed.json
{
  "event": "preauthorization.capture.failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

preauthorization.capture.success

documented official schema

Preauthorized amount is captured

Identified by event field in the body Resource preauthorization

paystack-preauthorization-capture-success.json
{
  "event": "preauthorization.capture.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

preauthorization.release.failed

documented official schema

Releasing a preauthorization hold fails

Identified by event field in the body Resource preauthorization

paystack-preauthorization-release-failed.json
{
  "event": "preauthorization.release.failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

preauthorization.release.success

documented official schema

Preauthorization hold is released

Identified by event field in the body Resource preauthorization

paystack-preauthorization-release-success.json
{
  "event": "preauthorization.release.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

preauthorization.reserve.success

documented from Paystack docs (example)

Preauthorization hold is placed on a card

Identified by event field in the body Resource preauthorization

paystack-preauthorization-reserve-success.json
{
  "event": "preauthorization.reserve.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

refund

refund.failed

documented official schema

Refund can't be processed, and the amount returns to your balance

Identified by event field in the body Resource refund

paystack-refund-failed.json
{
  "event": "refund.failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

refund.needs-attention

documented from Paystack docs (example)

Refund reaches the needs-attention status

Identified by event field in the body Resource refund

paystack-refund-needs-attention.json
{
  "event": "refund.needs-attention",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

refund.pending

documented official schema

Refund starts and waits on the processor

Identified by event field in the body Resource refund

paystack-refund-pending.json
{
  "event": "refund.pending",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

refund.processed

documented official schema

Processor completes a refund

Identified by event field in the body Resource refund

paystack-refund-processed.json
{
  "event": "refund.processed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

refund.processing

documented official schema

Processor receives a refund

Identified by event field in the body Resource refund

paystack-refund-processing.json
{
  "event": "refund.processing",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

subscription

subscription.create

documented from Paystack docs (example)

New subscription is created

Identified by event field in the body Resource subscription

paystack-subscription-create.json
{
  "event": "subscription.create",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

subscription.disable

documented from Paystack docs (example)

Subscription is disabled

Identified by event field in the body Resource subscription

paystack-subscription-disable.json
{
  "event": "subscription.disable",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

subscription.expiring_cards

documented official schema

Monthly list of subscriptions whose cards expire that month

Identified by event field in the body Resource subscription

paystack-subscription-expiring-cards.json
{
  "event": "subscription.expiring_cards",
  "data": [ … ]
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

subscription.not_renew

documented from Paystack docs (example)

Subscription turns non-renewing, so its next charge won't run

Identified by event field in the body Resource subscription

paystack-subscription-not-renew.json
{
  "event": "subscription.not_renew",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

transfer

transfer.failed

documented from Paystack docs (example)

Outgoing transfer fails

Identified by event field in the body Resource transfer

paystack-transfer-failed.json
{
  "event": "transfer.failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

transfer.reversed

documented from Paystack docs (example)

Outgoing transfer is reversed

Identified by event field in the body Resource transfer

paystack-transfer-reversed.json
{
  "event": "transfer.reversed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

transfer.success

documented official schema

Outgoing transfer completes

Identified by event field in the body Resource transfer

paystack-transfer-success.json
{
  "event": "transfer.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

Other Paystack events

bank.transfer.rejected

documented from Paystack docs (example)

Customer's bank transfer is rejected, for example for a wrong amount

Identified by event field in the body

paystack-bank-transfer-rejected.json
{
  "event": "bank.transfer.rejected",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

customeridentification.failed

documented from Paystack docs (example)

Customer identity validation fails

Identified by event field in the body

paystack-customeridentification-failed.json
{
  "event": "customeridentification.failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

customeridentification.success

documented from Paystack docs (example)

Customer identity validation passes

Identified by event field in the body

paystack-customeridentification-success.json
{
  "event": "customeridentification.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

dedicatedaccount.assign.failed

documented from Paystack docs (example)

Dedicated virtual account can't be assigned to a customer

Identified by event field in the body

paystack-dedicatedaccount-assign-failed.json
{
  "event": "dedicatedaccount.assign.failed",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

dedicatedaccount.assign.success

documented from Paystack docs (example)

Dedicated virtual account is assigned to a customer

Identified by event field in the body

paystack-dedicatedaccount-assign-success.json
{
  "event": "dedicatedaccount.assign.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

direct_debit.authorization.active

documented official schema

Direct debit authorization becomes chargeable

Identified by event field in the body

paystack-direct-debit-authorization-active.json
{
  "event": "direct_debit.authorization.active",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

direct_debit.authorization.created

documented official schema

Customer approves a direct debit authorization request

Identified by event field in the body

paystack-direct-debit-authorization-created.json
{
  "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

Send example to Inspect → View as JSON

paymentrequest.pending

documented from Paystack docs (example)

Payment request goes out to a customer

Identified by event field in the body

paystack-paymentrequest-pending.json
{
  "event": "paymentrequest.pending",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

paymentrequest.success

documented from Paystack docs (example)

Customer pays a payment request

Identified by event field in the body

paystack-paymentrequest-success.json
{
  "event": "paymentrequest.success",
  "data": { … }
}

From Paystack docs

  • Content type application/json

Send example to Inspect → View as JSON

zero_charge_authorization.failed

documented No payload yet

Zero-amount card authorization fails

Identified by event field in the body

No payload yet.

Help fill this in → View as JSON

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.

Not affiliated with Paystack. Facts are compiled from public sources and linked inline.