Active paid patrons appear in billing history but are missing from /identity OAuth2 memberships response

API Feedback
1

Hi Patreon Developers team,
We are seeing a critical issue with our campaign (Campaign ID: 497683).
Some patrons have successfully paid and appear in Patreon billing history, but when we call the OAuth2 /identity endpoint using the patron’s own access token, the response does not return the expected membership for our campaign.
Endpoint
GET https://www.patreon.com/api/oauth2/v2/identity?include=memberships.currently_entitled_tiers,memberships.pledge_history&fields[user]=full_name,email&fields[member]=last_charge_status,campaign_lifetime_support_cents,currently_entitled_amount_cents
Expected
If a patron has successfully paid, /identity should return membership data for our campaign, including fields like:

  • last_charge_status
  • currently_entitled_amount_cents
  • currently_entitled_tiers
    Actual
    For some paid patrons, the memberships data is empty or does not include Campaign ID: 497683, even though their payment is visible in billing history.
    Affected users
  • Patreon User ID: 208115933
  • Patreon User ID: 209768503
    Impact
    Because our system relies on /identity to verify membership and unlock rewards, these patrons were incorrectly denied access, which led to complaints, refund requests, and cancellations.
    Questions
  1. Why would billing history show a completed payment while /identity does not return the membership?
  2. Is there a known delay or sync issue between payment completion and API membership availability?
  3. Are there intermediate states like pending or payment_processing that would cause this behavior?
  4. What is the recommended way to reliably detect newly paid patrons before /identity is updated?
  5. Could someone investigate these affected accounts?
    For privacy reasons, we have omitted email addresses from this public post and can provide them privately if needed.
Campaing id of membership via API
2

The member record update/creation can have a slight delay, however it should not last long typically.

I think this is an edge case / bug that I reported to the responsible team, they’ll investigate. I would suggest filing a support ticket if you want to get updates, alternatively once I hear more I can post here.

Thanks for the report!

3

For the 2 users I mentioned, they contacted us weeks after completing their sponsorship, but still couldn’t retrieve pledge history through the identity endpoint.

4

Is there any progress?