Stripe webhook fields missing depending on payment method (card vs. link)

[amas]

Hi team,

I’m building a workflow where Stripe payments trigger a process that stores customer data and calculates VAT based on the buyer’s country.

The problem is: depending on the payment method (card vs. link), some key fields are missing in the webhook payload.

Here’s what I’ve observed:

• For most card payments (especially from Spain), the country is available under:
  data.object.billing_details.address.country
  and/or
  data.object.payment_method_details.card.country.
• For Stripe Payment Link payments, often only
  data.object.payment_method_details.link.country
  is available, and billing_details.address.country is frequently missing.

The issue is that when creating the workflow in Pabbly, I can only use the fields present in the sample data. This means I can’t configure logic that checks or uses both paths (card vs. link), because the missing fields aren’t recognized unless they’re in the sample.


My question is:

• Is there a way to reference both possible fields, even if one is missing in the sample?
• Or can I somehow load a custom test payload that includes all relevant fields, so I can build a more robust flow?

Thank you in advance for your help!

Best regards,

Antonio

 

[ArshilAhmad]

Hi @amas,

Your concern appears to be similar to the following one:

How to Handle Different Webhook Payloads

We have some webhooks that we receive that have different fields and pieces of information and we don't have a way to change this. For example, one of our providers sends out all event notices to a single webhook and different types of events have different fields included. This causes a...

forum.pabbly.com

In case the label changes in the response received from your webhook, you’ll need to follow these steps: first, capture the initial payload and set up Route 1. Then, click on 'Re-Capture Webhook Response' to capture the second payload (with a different label) and set up Route 2. Repeat this process—clicking 'Re-Capture Webhook Response' to capture each new payload and setting up the corresponding routes accordingly.

Watch the video shared below (Here, I have captured the payload manually, but you will need to send the payload from your source application.):

google_screen_recording_2025-04-20T20-12_23.198Z.webm

drive.google.com

You may notice that in one of your routes, depending on the data captured at that time in your trigger step, some mapped fields appear to be missing. However, during automation, if those fields are present in the payload of the trigger step, they will be passed to the relevant steps.

 

[amas]

Thanks a lot — that really clears it up!


I just wanted to add a quick note for future readers or the dev team, as this detail might save someone hours of confusion:


As you said: Even if a mapped field appears as “missing” or shows an error during setup, it will still work correctly during automation, as long as the field is present in the actual payload at runtime — that’s a key insight and super helpful to know.


However, keep in mind that if you try to edit a later step in your workflow and reference a field that wasn’t included in the last captured payload, you won’t be able to save the step. So it’s important to re-capture the correct payload with that field included before editing.


Again, thank you — this really helped me move forward!

 

[ArshilAhmad]

Thank you for the update and your insights. We're pleased we were able to assist you. We’d love to hear your feedback, and it would mean a lot if you could leave us a quick review on Google.