# Inquiry: Duplicate loyalty.account.updated Webhook with Same Event ID but Different Balance Points

**URL:** <https://developer.squareup.com/forums/t/inquiry-duplicate-loyalty-account-updated-webhook-with-same-event-id-but-different-balance-points/23847>\
**Category:** Questions\
**Tags:** loyalty-api\
**Created:** [September 3, 2025, 6:54am UTC](https://developer.squareup.com/forums/t/inquiry-duplicate-loyalty-account-updated-webhook-with-same-event-id-but-different-balance-points/23847 "2025-09-03T06:54:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![murphyzhang](https://avatars.discourse-cdn.com/v4/letter/m/fbc32d/32.png) [@murphyzhang](https://developer.squareup.com/forums/u/murphyzhang)\
**Post date:** [September 3, 2025, 6:54am UTC](https://developer.squareup.com/forums/t/inquiry-duplicate-loyalty-account-updated-webhook-with-same-event-id-but-different-balance-points/23847/1 "2025-09-03T06:54:54Z")

</div>

Dear Square Support Team,

I encountered an unusual issue with the `loyalty.account.updated` webhook. On **2025-08-28** , our system received two webhook deliveries for the same loyalty account within one second. Both had the **same `event_id` (`c7aea4eb-3335-39b9-9dea-5f3aa8cc2d48`)**, but the `balance_points` values were different (`30` and `25`).

**Loyalty Account ID: `35d0ec21-6262-46cb-93e9-31e33088e21d`**

 ![image](https://global.discourse-cdn.com/square/original/2X/1/1c8e6258df1db90ecff4e74ed812e86fd7ceaffe.png)

When I checked the Square Webhook Logs, I only found one payload for that event ID, not two.

As I understand, each event ID should map to a single consistent payload. Could you please confirm if this behavior indicates a webhook delivery anomaly on Square’s side?

Thank you for your assistance, and I look forward to your clarification.

Best regards,

Murphy

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [September 3, 2025, 6:55am UTC](https://developer.squareup.com/forums/t/inquiry-duplicate-loyalty-account-updated-webhook-with-same-event-id-but-different-balance-points/23847/2 "2025-09-03T06:55:11Z")

</div>

👋 I’m Square Dev AI, here to help answer your question!  
Based on the information you’ve provided, the following documentation will help answer your question:

> **[Search for Loyalty Events](https://developer.squareup.com/docs/loyalty-api/loyalty-events)**
>
> Learn about the LoyaltyEvent object and how to use the Square Loyalty API to list or search for events that affect the point balance of loyalty accounts.

> **[Payments API Webhooks](https://developer.squareup.com/docs/payments-api/webhooks)**
>
> Learn about the Square webhook notifications supported by the Payments API.

> **Additional Documentation**
>
> [Webhook Event Logs](https://developer.squareup.com/docs/devtools/webhook-logs)  
> [Manage Loyalty Points](https://developer.squareup.com/docs/loyalty-api/loyalty-points)  
> [Use Webhooks to Integrate with a Payroll System](https://developer.squareup.com/docs/labor-api/webhooks)

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.  
Otherwise one of our Developer Advocates will provide additional assistance shortly.

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [September 3, 2025, 3:53pm UTC](https://developer.squareup.com/forums/t/inquiry-duplicate-loyalty-account-updated-webhook-with-same-event-id-but-different-balance-points/23847/3 "2025-09-03T15:53:41Z")

</div>

I checked our logs and I only see one webhook for that `event_id`. The balance of the account is 30 but they also have expiring points that is 25 points. Did something get logged incorrectly between the values which is possibly why you see two logs for the same event? 🙂
