Modem Pay supports specifying a callback URL per payment intent. This allows you to receive event notifications for that specific payment directly at the URL you provide, overriding your global webhook URL.
The same types of events (such as payment_intent.created
, payment_intent.succeeded
, payment_intent.failed
, etc.) are sent to your callback_url
. The process for handling these events is almost identical, except for the authentication method (see below). For more details on event types and recommended handling, refer to the Webhooks documentation.
When creating a payment intent, you can include an optional callback_url
parameter to specify where you want Modem Pay to send event notifications related to this payment.
callback_url
is provided in the payment intent, Modem Pay sends event notifications (e.g., payment_intent.succeeded
, payment_intent.failed
) to this URL instead of your global webhook URL.callback_url
is set, events are sent to your global webhook as usual.callback_url
include an x-modem-signature
header containing a signature that is signed with your merchant secret key for authentication.For complete webhook validation examples in other programming languages (Python, Go, etc.), please refer to our Webhooks documentation. When validating callback URL events, use your merchant secret key instead of the webhook signing key.
This differs from the global webhook which uses a separate signing key and payload signatures for verification.
To secure your endpoint:
x-modem-signature
header.Modem Pay supports specifying a callback URL per payment intent. This allows you to receive event notifications for that specific payment directly at the URL you provide, overriding your global webhook URL.
The same types of events (such as payment_intent.created
, payment_intent.succeeded
, payment_intent.failed
, etc.) are sent to your callback_url
. The process for handling these events is almost identical, except for the authentication method (see below). For more details on event types and recommended handling, refer to the Webhooks documentation.
When creating a payment intent, you can include an optional callback_url
parameter to specify where you want Modem Pay to send event notifications related to this payment.
callback_url
is provided in the payment intent, Modem Pay sends event notifications (e.g., payment_intent.succeeded
, payment_intent.failed
) to this URL instead of your global webhook URL.callback_url
is set, events are sent to your global webhook as usual.callback_url
include an x-modem-signature
header containing a signature that is signed with your merchant secret key for authentication.For complete webhook validation examples in other programming languages (Python, Go, etc.), please refer to our Webhooks documentation. When validating callback URL events, use your merchant secret key instead of the webhook signing key.
This differs from the global webhook which uses a separate signing key and payload signatures for verification.
To secure your endpoint:
x-modem-signature
header.