How can I verify that my webhook URL can receive notifications

You can send test notifications to the webhook URL during configuration in the user interface. This ensures the webhook setup is correct before enabling the notifications feature.

I'm not receiving webhooks anymore, am I alerted when something goes wrong

Peach Payments sends an automated daily email to all configured webhook email addresses to alert you when notifications fail to deliver. Upon receiving such an alert, you must fix the webhook URL accessibility. This ensures Peach Payments retries the failed notifications on the next defined retry interval and they are satisfactorily delivered. Failure to act results in losing all notifications beyond the retry period.

Can I configure multiple email addresses to get alerted when webhooks are failing

Yes. You can configure multiple email addresses to receive the daily alerts. Consider updating the email addresses in case people change roles or leave the company.

What is the lead time to remediate the webhook URL so that I recover all failed notifications

Peach Payments retries failed notifications based on the documented retry intervals, but the retrial process does not exceed 30 days.

Why am I not receiving all the webhooks

Verify that you have configured the correct webhook URL, check your firewall restrictions, and perform a Click to Test from the user interface to validate accessibility.

Why am I not receiving webhooks from time to time

Verify that your server for receiving notifications is able to handle peak-loads of messages. When processing goes to higher transactions per second rates, then you should expect to receive the same or more notifications per second. If your webhook server cannot consume all the notifications, then your webhook URL listener might become slower and from time to time become unreachable.

How do I know to which transactions the notification updates are referring to

If the notification is for a transaction status change, you receive at least one of the following data points: id, referenceId, registrationId, or merchantTransactionId. You can use these fields to match your transaction data against the webhook message.

What is the best way to handle the webhook URL connection

For PCI DSS compliance, SSL (Secure Socket Layers) connections using untrusted certificates are not allowed. Ensure you have a valid SSL certificate chain. Self-signed certificates are not valid.