#vell2x_best-practices

1 messages ¡ Page 1 of 1 (latest)

thorn plazaBOT
#

👋 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/1393235181288034344

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

vocal hazel
#

Hi, you do not need to create a new PaymentIntent. You can retrieve the PaymentIntent when your customer comes back online to pay. You'd retrieve the client_secret from that already created PaymentIntent and the confirm the payment after collecting the payment method details.

serene tendon
#

Should I store the secret in the metadata? I am unclear how Stripe will know what intent I want to pay for.

vocal hazel
#

No, you can retrieve the PaymentIntent and the get the client_secret . We do not recommend storing that in the metadata

#

You can track that on your end, that is going to come from your integration

#

By way of log in etc, you know when your customer is back. You then make a GET call to attain the PaymentIntent and get the client_secret

serene tendon
#

So we have packages on the app. Lets say the customer orders the same package twice but pays for neither. How would I be able to select item one to pay for? I do have unique values such as job id in the metadata if that helps.

vocal hazel
#

You'd track that on your end and use the metadata you're already passing to identify