Webhooks
Overview
Webhook
Use for the following events
Workflow

Hash signature calculation
Failing Webhooks Alerts
Related pages
Last updated
Was this helpful?
2Checkout generates automatic notifications for transaction and subscription/license change events, which it sends to a location on your server that you control. You can perform backend tasks, including provisioning, entitlement, customer and subscription lifecycle management, and more by using 2Checkout’s IPNs, LCNs, and API message services on your server.
Purchase and transactions events: - Authorized payments - Finalized payments - Refunds - Chargebacks - Creating customers
Subscription events: - Renewal - Expiration - Upgrade - End user info updates
2Checkout’s webhooks (IPN and LCN) operate asynchronously.

Depending on your shoppers' location, addresses and billing names may contain special characters.
For UTF-8 characters, the length in bytes can be longer than the string length. When calculating the hash signature, we highly recommend using multibyte methods that return the number of bytes in a string, instead of methods that return the number of characters. For example, if using PHP, use the strlen method instead of length.
You can configure alerts for IPN and LCN failing webhooks from your Merchant Control Panel by following these steps:
Select the frequency (receive an email every X hours) for which you want to be alerted and the threshold of failing IPNs/LCNs webhooks. Example: the platform will send an email every 4h when more than 25% of the IPNs are failing.

The alert will be sent to the email address filled out in the Technical notifications email field under Account settings → Account information in your Merchant Control Panel. If the 'Technical notifications email' is not filled out, you will not be able to configure the email alert for the failing webhooks.
Last updated
Was this helpful?
Was this helpful?