Hi @Jaingram 

Good question.

Have you tried adding this as Step 2?

Action: Stripe - Find Transactions

Thanks for the idea, I did try adding adding Find New Payment, (also tried Find Charge)..  Not sure the difference.  But it too, does not pull the meta.  Weird thing is, I can go and edit the Zap, and select Find New Records, and it finds that record and it has all the meta.   It’s just on the initial that it’s missing..  Wonder if a pause would help.  I’ll try that and report back..

@Jaingram 

Also, make sure to configure/test with a trigger example that you know has metadata.

Yep, they all do, and unfortunately the delay didn’t help.  The head scratcher is definitely the fact I can go in and edit the Zap and pull new records and it will pull this one in with all the meta data.  Really hope they fix this as all our stripe transactions are broken and have to be inputted manually.  Going to have to start looking at new vendors if this keeps up.

@Jaingram 

Can you post screenshots with how your Zap steps are configured?

Let me know if there is a step you would like to see more detail..
 

@Jaingram 

Perhaps try this Zap trigger.

I’ve got metadata configured on Stripe Payment Links that comes thru when using this trigger.

Where is the metadata set? (Product, Price, etc.) .screenshots]

I’ll try that and will send the meta set if it fails again. 

Tried the Checkout Session step and it will not find any new transactions.  Probably because of the way we are taking donations.  Our donation page is here:  https://us.langham.org/donate/

Regarding the meta, just to show an example.  We just had a transaction fail and I went in and edited the Zap and clicked Find new records from the first step and it found the one that failed and the meta data is there:
 

However, if I go in to the Zap run that failed, and look at the “Data Out” that same data is missing entirely, the whole section is missing..

@Jaingram 

Another workaround to try is using the Stripe API: https://stripe.com/docs/api

Zap action: Stripe - App Extensions

There is an AI assist to help configure.

Looks like if I delay it for 2 hours the meta data is there.  Not 1 hour, but 2.  Any ideas why it would take 2 hours?

Hi there @Jaingram!

Glad to hear you were able to see the meta data after adding a delay to the Zap. I took a look at the internal notes we have for the Stripe app but couldn’t see any reference on how often the data the API sees is refreshed.

From Stripe’s API documentation it appears that data will be refreshed with one day: https://stripe.com/docs/stripe-data/available-data. But it could be that time frame is the maximum amount of time that it could take to update, or perhaps it’s only nearer 24 hours for certain kinds of data that’s been updated. 

Usually for situations like this setting a delay to a 2-5 mins given the API enough time to catch up to the new data. Did you test out the delay of 1 hours over one or multiple days? Just thinking that maybe on the day of testing Stripe’s servers were experiencing heavier use than normal or had an issue that slowed things down? 

Do you think that could be the case here? 

The crazy thing is, the “legacy” Zap, (older version) is immediate and continues to work.  This new one used to be immediate back in the summer but broke around September where it is now taking several hours.  It would seem it is a coding issues since the legacy Zap continues to work and meta is available immediately.

Apologies for missing your reply here previously, @Jaingram!

Crazy indeed! I just started digging further into this and it seems that you also reached out to our support team who added you to a bug where the Stripe New Payment Trigger isn’t returning metadata when Zap runs live. It looks as though that issue is still ongoing but we’ll be sure to email you as soon as it’s fixed.

Hopefully that workaround of adding a delay action to the Zap will continue keep things running until that’s sorted. Please do reach out again if we can help with anything else in the meantime. 

Hi

Any update since then? I am having the same issue regarding fetching metadata from Stripe. It worked during the Zap setup after Publish, but no luck after that. 

Any work around to share from experts?

I continue to have a 2 hour timer on the Zap.  So far, that has worked.  

Welcome @YGN, and hi again @Jaingram 

I’ve just checked on the bug report and it appears that the Stripe API does not require customer information to successfully process a payment, so if the customer is processing a payment without providing personal data, no customer metadata will shown on the webhook information coming into Zapier. So the customer metadata not coming through with the Stripe New Payment Trigger appears to be the expected behaviour in some cases so the bug report been marked as closed. 

There’s been a workaround suggested on the bug report that I wanted to pass on here in case it works better than setting a 2 hour delay in the Zap:

Hope that helps. Please keep us updated on how you get on with the Checkout Session Completed trigger, keen to know whether that does the trick! 

We insert all the metatdata into the transaction.  All the data is in the transaction as long as you wait for around 2 hours for it to appear.  This is something that worked fine previously and with the last update you broke it.  It is still working on the previous version of the Stripe trigger.

We are a non profit Company with Stripe for receiving donation. Have been trying Zapier with its automation in getting data from Stripe and sharing the data in a customised ways for people in finance and fund raising team. We do inject essential information in Stripe during donation as meta data and expect to retrieve them back. Time is running short and we have only 1-2 days for the trial. Today I tried the 2-hr delay, but it is not working in my case. 

Also, I am not sure what personal information required for Stripe for a credit card payment in return to release the metadata. As a normal credit card payment, Stripe only asks for essential card info, however, I can see customer name and all the personal info in Stripe transaction DB. What else are missing?

Don’t Zapier think it is so strange that we can get all the meta data if we do it in “transfer data” as a one-off batch retrieval of data, but cannot get it during Zap one by one. We might give up if this cannot be done caused Stripe also allows us to customise and get the report in traditional manner. 

So, it’s been about a year since this bug originally was found, and yet, there’s still no fix. This used to work fine. Are you still using the 2h delay thing? It’s just ridiculous to be honest.

​@Troy Tessalone Hello Troy. It’s been about a year since this bug originally was found, and yet, there’s still no fix. This used to work fine. Are there any news? Thank you.

​@RationalLunatic 

I do not work for Zapier.

You can try opening a ticket with Zapier Support for more info: https://zapier.com/app/get-help