# Understanding a paid patreon that never got a webhook

**URL:** <https://www.patreondevelopers.com/t/understanding-a-paid-patreon-that-never-got-a-webhook/8652>\
**Category:** Friendly Help\
**Created:** [March 4, 2024, 3:33pm UTC](https://www.patreondevelopers.com/t/understanding-a-paid-patreon-that-never-got-a-webhook/8652 "2024-03-04T15:33:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ParoX](https://avatars.discourse-cdn.com/v4/letter/p/cab0a1/32.png) [@ParoX](https://www.patreondevelopers.com/u/ParoX)\
**Post date:** [March 4, 2024, 3:33pm UTC](https://www.patreondevelopers.com/t/understanding-a-paid-patreon-that-never-got-a-webhook/8652/1 "2024-03-04T15:33:22Z")

</div>

I am trying to make sense of why the UI says this user has paid, but I never got a member:update webhook that says they had paid. Only that it was pending and then declined

Here you can see all the webhooks that I got, I only have one tier:

> **[CSV Sense - Online CSV Editor - Online CSV Viewer - Online Data Visualisation...](https://csvsense.com/mQAe61pKXBRWhZ3n/-/)**
>
> CsvSense is a free online CSV editor, CSV viewer and Data Visualisation tool that allows you to effortlessly edit, inspect CSV files and create and share charts from your CSV data. Take advantage of our online CSV editor to make changes and view the...

Once I got a `members:pledge:create` with `currently_entitled_amount_cents > 0` I gave them access, but it was pending, then when I got the declined status I removed access. However on the Patreon UI it says this user has paid:

 ![brave_NqGxYqQXqH1](https://canada1.discourse-cdn.com/flex036/uploads/patreondevelopers/original/2X/6/63a931c584d482fb3f6405238451df8696981687.png)

How should I interrupt the webhooks I received in order to handle this use-case? Verifying their current status via OAuth login is not feasible as I do not offer/want Patreon login.

---

<div class="post-metadata">

**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\
**Post date:** [March 5, 2024, 6:49pm UTC](https://www.patreondevelopers.com/t/understanding-a-paid-patreon-that-never-got-a-webhook/8652/2 "2024-03-05T18:49:22Z")

</div>

A payment can be declined at first and then succeed after a few retries at Patreon side. So if you have a need to have more granular control of the reward distribution, you could go the route of regularly syncing your campaign to your local app in addition to the webhooks and check the exact status of the patron at a given time. If you are distributing rewards by having users log into your app/site, its easier - just use the user’s access token to check for currently\_entitled\_tiers and currently\_entitled\_amount\_cents.

---

<div class="post-metadata">

**Author:** ![ParoX](https://avatars.discourse-cdn.com/v4/letter/p/cab0a1/32.png) [@ParoX](https://www.patreondevelopers.com/u/ParoX)\
**Post date:** [March 5, 2024, 7:03pm UTC](https://www.patreondevelopers.com/t/understanding-a-paid-patreon-that-never-got-a-webhook/8652/3 "2024-03-05T19:03:17Z")

</div>

I understand that, I’m just confused why a “paid” status was never sent. Should I assume if currently\_entitled is set that the payment went through even if I get repeated declined afterwards? Please see the csv linked to see

---

<div class="post-metadata">

**Author:** ![codebard](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/codebard/32/14_2.png) [@codebard](https://www.patreondevelopers.com/u/codebard)\
**Post date:** [March 12, 2024, 9:52pm UTC](https://www.patreondevelopers.com/t/understanding-a-paid-patreon-that-never-got-a-webhook/8652/4 "2024-03-12T21:52:33Z")

</div>

currently\_entitled\_tiers and currently\_entitled\_amount cents should correctly show what a user is entitled to at any moment without needing to check the payment status. If you are able to use them, use them without anything else unless your rewards are rewards that cannot be withdrawn if something goes amiss with the user’s payment later.
