Skip to main content
Here are the events a webhook can subscribe to:
  • transfer.created
  • transfer.processing
  • transfer.succeeded
  • transfer.failed
  • transfer_irt.created
  • transfer_irt.processing
  • transfer_irt.succeeded
  • transfer_irt.failed
  • payment_intent.created
  • payment_intent.processing
  • payment_intent.succeeded
  • payment_intent.action_required
  • payment_intent.payment_failed
  • payment.created
  • payment.pending
  • payment.succeeded
  • payment.action_required
  • payment.failed
Recurring debits of scheduled subscriptions also trigger payment.succeeded and payment.failed. Their data has no payment id or intentId and contains subscriptionId, customerId, transactionReference and amount. If your endpoint already handles payment.succeeded or payment.failed, check for data.subscriptionId before reading data.id: when it is present, the event is a subscription debit and has no data.id.
  • deposit.created
  • deposit.pending
  • deposit.success
  • deposit.failed
  • refund.created
  • refund.pending
  • refund.pending_manual
  • refund.successful
  • refund.failed
  • payment_refund.created
  • payment_refund.pending
  • payment_refund.pending_manual
  • payment_refund.successful
  • payment_refund.failed
  • provisioning.created
  • provisioning.succeeded
  • provisioning.failed
  • receipt.created
  • sms.created
  • sms.sent
  • sms.received
  • sms.failed
  • transaction.payment_collected
  • transaction.deposit
  • provider.wave
  • submerchant.created
  • submerchant.updated
  • subscription.created
  • subscription.suspended
  • subscription.cancelled
  • settlement_request.submitted
  • settlement_request.processing
  • settlement_request.funds_sent
  • settlement_request.confirmed
  • settlement_request.rejected