In the sandbox environment, you can trigger
VENDOR_SETTLEMENT_INITIATED, VENDOR_SETTLEMENT_SUCCESS and VENDOR_SETTLEMENT_FAILED on demand. Use the Simulate Vendor Settlement API instead of waiting for a real settlement cycle. VENDOR_SETTLEMENT_REVERSED is not simulated. To test a reversal, settle to the Success (later reversed) test account instead.To receive these webhooks, go to Payment Gateway > Developers > Webhooks on the Merchant Dashboard. Subscribe to each event separately using webhook version 2025-01-01. This is the webhook subscription version you select for each event, not the x-api-version header you send on your API calls. Subscribing to VENDOR_SETTLEMENT_SUCCESS does not enable VENDOR_SETTLEMENT_INITIATED. Vendor settlement webhooks are not delivered on any other webhook version.Vendor settlement initiated
Cashfree triggersVENDOR_SETTLEMENT_INITIATED when it initiates a vendor settlement.
For the initiated event, the webhook
type is VENDOR_SETTLEMENT_INITIATED while the settlement status inside the payload is CREATED. Check for CREATED when you verify this payload.Vendor settlement success
Vendor settlement failed
Vendor settlement reversed
Payload field description
Reasons for failed and reversed settlements
Signature verification
The signature must be used to verify if the request has not been tampered with. To verify the signature at your end, you will need your Cashfree PG secret key along with the payload. timestamp is present in the header x-webhook-timestampActual signature is present in the header x-webhook-signature