#f3ax_api

1 messages ¡ Page 1 of 1 (latest)

shrewd ferryBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1316473650488148008

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

keen cedar
#

However, the customer does have a payment method.

hot coral
keen cedar
#

Okay can you look at the request let me know if you see anything wrong in that?

#

Because I am not sure if this is a Zapier problem, this is still a direct stripe integration and I am making a normal request to the API, and it used to work okay, was there any recent updates or something?

shrewd ferryBOT
spark quarry
keen cedar
#

req_1XnjlRnsJ5dj9Q

#

This is the latest one

spark quarry
#

Have you checked if the customer has any associated payment methods?

#

I don't see any attached PaymentMethods for this customer

keen cedar
#

Yes there is an ID starting with pm_

spark quarry
#

Can you share it in text?

keen cedar
#

pm_1QUHO7K8dZuyTTEKefDwAknY

#

hmm I see what you are saying about no attached PaymentMethod

spark quarry
#

Yup, I think this PaymentMethod was used at some point but wasn't really attached to the customer

#

so the API wouldn't really return it

keen cedar
#

The $50 charge has a PM but the customer not?

spark quarry
#

When the charge was made, was the request configured to set up the payment method for future use?

keen cedar
#

Yeah it always is

spark quarry
#

Can you share the PaymentIntent?

#

it should start with pi_xxx

keen cedar
#

pi_3QUHO9K8dZuyTTEK1utQyIHn

spark quarry
#

Thanks

keen cedar
#

Let me double check that too

#

No problem thanks for the help

spark quarry
keen cedar
#

Okay so I have two options in my form, "Authorize payment for future capture" and Attach payment method to customer

#

which one enables setup future usage

#

that should be attach payment method to customer right?

#

and one more thing please, if I use the same pm_ ID that was attached previously would it work to run this situation?

spark quarry
#

If your request sends setup_future_usage parameter then yeah, the payment method should get attached..

Since the payment method was already consumed once, you can't save it again. You'd need to recollect it from the customer

keen cedar
#

Okay, thank you so much you were a big help.