Callback Identification

When using HPP or accepting multiple payment methods, Exirom appends explicit identifiers to every callback URL so you can determine the correct DTO and parsing logic before reading the body.

#Identification Fields

#paymentMethod (Query Parameter)

All callbacks are sent as HTTP POST requests. Exirom appends paymentMethod to the callback URL regardless of the original callbackUrl provided.

#apmType (Query Parameter and Payload Field)

When paymentMethod=apm, apmType is appended to the URL and included in the payload body.

• Present only when paymentMethod=apm
• Value matches the Supported Payment Methods (PaymentMethod) enum
• Use it to select the correct parser before reading the body

#Callback URL Examples

Given the original callback URL:

https://merchant.com/payment-status

Exirom invokes one of the following:

Card payment:

POST https://merchant.com/payment-status?paymentMethod=card

APM payment:

POST https://merchant.com/payment-status?paymentMethod=apm&apmType={APM_METHOD}

Example:

POST https://merchant.com/payment-status?paymentMethod=apm&apmType=UPI_QR

#Parsing APM Callbacks (apmResponseData)

When paymentMethod=apm, the callback payload contains an apmResponseData field whose structure varies by apmType.

Do not assume apmResponseData has the same shape for all APMs. Always route parsing based on apmType.

Navigate to the relevant APM documentation page using the apmType value — each page describes the expected fields, redirect vs iframe behavior, and any required follow-up actions.

#Routing Summary

A single webhook endpoint can handle Card and all APM callbacks deterministically using these two query parameters.

#Related

• APM Response Data Examples — apmResponseData schemas by APM type
• Webhook Best Practices — signature verification, deduplication, polling fallback