Payment Webhook not Processed

Payment Webhook not Processed

Issue: The payment activity triggered to LSQ was not processed, resulting in no activity being logged against the lead. This was due to a delay of 9 days in the webhook response, exceeding LSQ's maximum acceptance delay of 7 days.

Solution: To ensure proper processing and logging of payment activity against leads, it is crucial to receive the webhook response within 7 days since payment initiation by the lead.

    • Related Articles

    • Automation Cards Failure email alerts

      The Automation Failure notification will trigger only those who created the automation and who modified the automation. Please note all the users who modified the automation will get the automation failure notification (e.g.: if user-a modified the ...

    • Opportunity owner update failure in the UI

      When an opportunity owner is tried to update "1 opportunity failed to update" error is shown. Whereas when the owner is updated via API it is successful. This happens because of the duplicate detection rule. If there are duplicate opportunities then ...

    • Discrepany in Whatsapp Report (Query)

      Issue: Why is the number of messages read on Whatsapp higher than the number of messages delivered? Solution: Sent successfully tracks messages from start to finish, including when a message is waiting to be sent, sent, delivered, and read and other. ...

    • Automation not trigger on owner/Lead update

      Hi Team, You may encounter an issue where Automation has not triggered on Lead update, where the field will be owner update. Reason To Debug this please check the owner update is done by which card/method. If Owner has been updated by "Lead ...

    • Lead Cohort Assignment | Gurnick and GEGI Integration

      Issue Raised: Leads not containing the right Cohort. Alternative/Associated Queries: 1) Leads in LSQ and Students in GEGI have different Cohort identifiers. 2) Registration Link is not being sent. 3) Lead is not updating in the as per GEGI data. ...