Handle Webhooks with Node.js SDK


Use callback verification to confirm that the callback you received from PhonePe is authentic.

The standard_phonepe_client.validate_callback method is used to validate webhook or callback responses. You can use this method by passing all the necessary parameters.

The request parameters are as follows:

Request Parameters
Parameter NameData TypeDescription
usernameStringYour unique username configured for the callback URL
passwordStringYour unique password configured for the callback URL
authorizationStringThe Authorization token sent in the callback response
responseBodyStringThe actual response body received in the callback as a string
Sample Request
import { StandardCheckoutClient, Env } from 'pg-sdk-node';
 
const clientId = "<clientId>";
const clientSecret = "<clientSecret>";
const clientVersion = <clientVersion>;  //insert your client version here
const env = Env.SANDBOX;      //change to Env.PRODUCTION when you go live
 
const client = StandardCheckoutClient.getInstance(clientId, clientSecret, clientVersion, env);
 
const authorizationHeaderData = "ef4c914c591698b268db3c64163eafda7209a630f236ebf0eebf045460df723a" // received in the response headers
const phonepeS2SCallbackResponseBodyString = "{\"type\": \"PG_ORDER_COMPLETED\",\"payload\": {}}"  // callback body as string
  
const usernameConfigured = "<MERCHANT_USERNAME>"
const passwordConfigured = "<MERCHANT_PASSWORD>" 
 
const callbackResponse = client.validateCallback(
    usernameConfigured,
    passwordConfigured,
    authorizationHeaderData,
    phonepeS2SCallbackResponseBodyString );
 
const orderId = callbackResponse.payload.orderId;
const state = callbackResponse.payload.state;

The function returns a CallbackResponse object containing two main parameters: type, which indicates the event type, and payload, which holds all the event-specific details.

Parameter NameData TypeDescription
typeCallbackTypeTells you what type of event happened (e.g., order completed, refund failed, etc.)
payloadCallbackDataContains all the details related to that event
  • The event type are explained below:
Callback TypeDescription
CHECKOUT_ORDER_COMPLETEDThe payment was successfully completed
CHECKOUT_ORDER_FAILEDThe payment failed
PG_REFUND_COMPLETEDA refund was successfully processed
PG_REFUND_FAILEDA refund request failed
PG_REFUND_ACCEPTEDPhonePe Payment Gateway acknowledged the refund request, but it’s not completed yet

The payload details are explained below:

CallbackData
Parameter NameData TypeDescription
merchantIdStringMerchant ID from which the request was initiated
orderIdStringOrder ID generated by PhonePe Payment Gateway (only for order callbacks)
originalMerchantOrderIdStringOrder ID generated by you (only for order callbacks)
refundIdStringRefund ID generated by PhonePe PG (only for refund callbacks)
merchantRefundIdStringRefund ID generated by you (only for refund callbacks)
stateStringThe current state of the order or refund.
amountLongThe amount processed in paisa.
expireAtLongThe expiry timestamp in epoch format
errorCodeStringThe error code (only for failed transactions)
detailedErrorCodeStringA more detailed error code (only for failures)
metaInfoMetaInfoMetadata passed during order initialization
paymentDetailsList<PaymentDetail>The Payment details of the transaction

The PaymentRefundDetail property contains a list of payment details for each payment attempt made against an order. The details of each payment are explained in the table below.

AttributeData TypeDescription
transactionIdStringMerchant ID from which the request was initiated
paymentModeStringOrder ID generated by PhonePe Payment Gateway (only for order callbacks)
timestampLongOrder ID generated by you (only for order callbacks)
stateStringAttempted transaction state. It can be any one of the following states:
COMPLETED
FAILED
PENDING
errorCodeStringError code (only present when the state is failed)
detailedErrorCodeStringA more specific error code (only present when the state is failed)

Exception handling in the PhonePe SDK is managed through the PhonePeException, which captures errors related to PhonePe APIs. It provides detailed information such as HTTP status code, error code, message, and additional error data to help identify and resolve issues effectively.

PhonePeException

Exception raised for errors related to PhonePe APIs.

AttributeDescription
codeThe status code of the http response.
messageThe http error message.
httpStatusCodeThe status code of the http response.
dataThe details of the error that happened while calling PhonePe.
Sample Request
import { StandardCheckoutPayRequest, StandardCheckoutPayResponse } from 'pg-sdk-node';
import { v4 as uuid } from 'uuid';
 
const merchantOrderId = uuid();
const redirectUrl = 'https://www.merchant.com/redirect';
 
const request = StandardCheckoutPayRequest.buidler()
  .merchantOrderId(merchantOrderId)
  .redirectUrl(redirectUrl)
  .build();
 
client.pay(request).then((response) => {
  const checkoutPageUrl = response.redirectUrl;
}).catch((error) => {
    const error = error as PhonePeException;  //error thrown is of PhonePeException type
    console.log(error.message);
});
  • InstrumentCombo
    • Represents a combination of the payment instrument and the payment rail used to complete a transaction.
Property Parameters
PropertyType
instrumentPaymentInstrumentV2Instrument used for the payment.
railsPaymentRailRail used for the payment.
amountlongAmount transferred using the above instrument and rail.
  • PaymentRail
    • Defines the type of rail used to initiate payment.
UPI RAIL
PropertyType
typePaymentRailType
utrString
upi_transaction_idString
vpaString
PG RAIL
PropertyType
typePaymentRailType
transaction_idString
authorization_codeString
service_transaction_idString
  • PaymentInstrumentV2
    • Represents the instrument used to initiate a payment. Various instrument types are listed below:
ACCOUNT
PropertyType
typePaymentInstrumentType
ifscString
account_typeString
masked_account_numberString
account_holder_nameString
CREDIT_CARD
PropertyType
typePaymentInstrumentType
bank_transaction_idString
bank_idString
arnString
brnString
DEBIT_CARD
PropertyType
typePaymentInstrumentType
bank_transaction_idString
bank_idString
arnString
brnString
NET_BANKING
PropertyType
typePaymentInstrumentType
bank_transaction_idString
bank_idString
arnString
brnString
EGV
PropertyType
typePaymentInstrumentType
cardNumberString
programIdString
WALLET
PropertyType
typePaymentInstrumentType
walletIdString

Now that you have learned how to verify the payment and what happens when the webhook fails, this concludes your website integration. The next step is to complete UAT testing and understand the process to go live.

Is this article helpful?