Webhooks (Payin)

Webhooks enable real-time notifications and data transfer between systems by sending HTTP POST requests to a specified call back URL when specific events occur. Note: It might happen that wowpe might call webhook multiple times with the same parameters. You are requested to handle such cases at your end using a client transaction ref field.

URL: https://yourdomainURL/api/PayoutAPI/Payoutnotify

{
    "OrderId": "100012213737",
    "Date": "6/24/2024 12:31:20 PM",
    "Status": 1,
    "ClientOrderId": "10445222",
    "Currency": "INR",
    "Amount": "1.0000",
    "OrderAmount": "100.0000",
    "RefNumber": "ENAN100011109351",
    "BankRRN": "417664215174",
    "MerchantId": "2213737",
    "PayerVPA": "test@ybl",
    "PayerMobile": "9876543210",
    "PayerName": "Test",
    "PaymentMode": "Intent",
    "Checksum": "8XmxsxO55BffnK57FWEhRZTM+b8BHWZrxATJ93jldTSmHgekU8H3zQU+77m481XVkSEc0JtkxVPjgjGBRqZN5cW5CyEjtr3+olIaorkUabMnVoPpcZOzi83NQm+m9p1ZVfpzrP4aDrTV2zuDOSLWiyZfCJwbxbMa995iGCfW9e/fO4LEsmaLRyCoyV6tXq3XyzwIIN5tTu2tkxPAOJFUXdsErzwZ8aQ66p+hNGYeiOnJrdPA0FuDoZ5cnJiKh7QhJEWgdoFXT7b5UrlvqYeUG5I8GylsJabP6ZOaT1wEHi0syGbqMW9aoyqE9g+kv0JU5Nfwc9HBR5ZzgIvH5G0nqi+E0hfVsKJaJm9vFmz/cQWsGFjwhnU3E8kS+WifnN/oJEMXCSDUv3nN47Bik4LF9bKuFwLumsd9g+YwNaTedZM="
}

Response Parameter:

KeyTypeDescription
OrderIdIntegerUnique Transaction Reference Number of wowpe
StatusIntegerFailed = 0,
Paid = 1,
Created = 2,
Attempted = 3,
Refund = 4,
Accepted = 5,
Expired = 6,
PartialPaid = 7,
Cancelled = 8,
ClientOrderIdStringUnique Client Reference Number of wowpe
PaymentModeIntegerIntent / Collect / QR
AmountStringActual Paid Amount against the Order.
OrderAmountStringOrder Requested Amount.
CurrencyStringINR
DateStringTxn Date
PayerNameStringName of Payer
PayerMobileStringMobile no of payer
Payer VpaStringPayer Virtual Payment address
MerchantIdStringMerchant ID
BankRRNIntegerUnique transaction Reference
RefNumberStringTransaction Reference Number of wowpe
ChecksumString (This
is optional
verification)
You can Use the Checksum to verify if the request has
not been tampered with. To verify the Checksum at
your end, you need your webhook secret key along
with the payload.
Step 1:
Generate the checksum at your end using the
payload and secret key at your end. Use AES-128 to generate checksum. IV will be default as
1234567890123456.

Step 2:
Convert the generated checksum to base64
string.

Step 3:
Match your generated checksum and the
checksum you received in the webhook. If it matches
accept the webhook else reject.