Webhook signature
You receive the webhook signature in the webhook header. The following table shows a sample header from a webhook request.Wallet credit events
Cashfree sends the following event when a wallet credit succeeds:
The following example shows a
PPI_CREDIT_SUCCESS webhook for a GIFT_PPI sub-wallet. The issued_gift_codes array appears only for gift wallets.
Wallet credit webhook payload fields
The webhook payload contains important metadata in its top-level fields.Wallet debit events
Cashfree sends a debit webhook when a wallet debit completes withSUCCESS. Webhooks are not sent while the debit is PENDING (for example, while OTP verification is in progress). For SMALL_PPI and FULL_KYC_PPI sub-wallets, the webhook is sent after you complete verification with the Verify Debit Wallet API.
Cashfree sends the following event when a wallet debit succeeds:
The webhook
data object uses status and status_code of SUCCESS. For other combinations returned by the Debit Wallet and Verify Debit Wallet APIs, see Status and status-code reference.
The following example shows a PPI_DEBIT_SUCCESS webhook for a GIFT_PPI sub-wallet. The applied_gift_codes array appears only for gift wallets.
Wallet debit webhook payload fields
The webhook payload contains important metadata in its top-level fields.Wallet refund events
Cashfree sends this webhook only when a refund completes successfully. Failed refunds or refunds that remainPENDING do not trigger a webhook.
Cashfree sends the following event when a wallet refund succeeds:
The following examples show
PPI_REFUND_SUCCESS webhooks for gift, closed-loop, and standard wallets. The refunded_gift_codes array is included only for GIFT_PPI refunds.
Wallet refund webhook payload fields
The webhook payload contains important metadata in its top-level fields.Wallet refund data fields
Thedata object contains the following fields:
Verify the signature before you process any webhook payload. For more information, see Webhook signature verification.