Stripe Integration Not Writing All Data | Community
Skip to main content
Answered

Stripe Integration Not Writing All Data

  • November 5, 2025
  • 2 replies
  • 89 views
P

Hi all, we use the Stripe integration from the Intercom App store, and I’ve found some cases in which not all of the Stripe data is populated when a subscription is created. 

Looking at the affected record in Stripe, I can see the event logs that reference data sent to Intercom but there are no errors present and the request body matches other Intercom users that DO have the subscription data. 

Is there any logging from the Stripe app in the Intercom marketplace where we can try and troubleshoot this? The best answer I got from Fin was “turn it on and off again” which might be the solution, but I’m hesitate to try that given how central this integration is to us. 

Best answer by Paul Byrne

Hey ​@prmichael Paul here from support engineering to help you out 🤝 

Thanks, we can troubleshoot this. Intercom logs app webhook deliveries internally , and we have an Admin Webhooks tool that can ping a subscription or temporarily kill deliveries for a host. To correlate what Stripe shows with what Intercom received, we need three pieces of evidence from you (Stripe event ID + payload, the Intercom app/workspace/App ID, and the affected user/company ID).

Once you provide those, I will look up delivery attempts and show you the request/response(s) from Intercom’s side, along with the mapping that shows which subscription fields were attached (or failed to attach).

 

Please open a conversation in Messenger so that the Support team can triage this for you.

    B

    2 replies

    Paul Byrne
    Intercom Team
    Forum|alt.badge.img+6
    • Paul ByrneIntercom Team
    • Intercom Team
    • Answer
    • November 6, 2025

    Hey ​@prmichael Paul here from support engineering to help you out 🤝 

    Thanks, we can troubleshoot this. Intercom logs app webhook deliveries internally , and we have an Admin Webhooks tool that can ping a subscription or temporarily kill deliveries for a host. To correlate what Stripe shows with what Intercom received, we need three pieces of evidence from you (Stripe event ID + payload, the Intercom app/workspace/App ID, and the affected user/company ID).

    Once you provide those, I will look up delivery attempts and show you the request/response(s) from Intercom’s side, along with the mapping that shows which subscription fields were attached (or failed to attach).

     

    Please open a conversation in Messenger so that the Support team can triage this for you.

    P
    thomasanderson
    Forum|alt.badge.img

    It looks like the issue isn’t with Stripe but with how the Intercom Stripe app is processing events. Since your Stripe event logs show clean payloads, the missing subscription data likely means Intercom never stored the event. Sadly, the Stripe app in Intercom doesn’t provide detailed logs.
    What usually works without breaking anything is re-syncing the integration, not fully disconnecting it. You can try:
    Intercom → App Store → Stripe → Reauthorize
    This forces a permissions refresh and triggers a clean event sync.
    If the issue continues, ask Intercom Support to manually reprocess the specific event IDs from Stripe — they can do it internally even though it’s not exposed in the UI.
     

    Thomas
    Terms & ConditionsAccessibility statement