noroup_code

[serene granite]

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• noroup_code, 1 day ago, 13 messages
• noroup_api, 1 day ago, 90 messages
• noroup_api, 1 day ago, 22 messages
• noroup_webhooks, 2 days ago, 17 messages
• noroup_webhooks, 2 days ago, 4 messages

[solid rampart]

hello! can you share the corresponding PaymentIntent id?

[next thunder]

Sure, one sec

pi_3Re4zNLbE4j2Km3D2wjmtD6n_secret_Z94hOMO1cFBIlDgTZXYW4TBXA

Seems like it just stays undefined regardless if the payment goes through or not

[solid rampart]

const { errorPay } = await presentPaymentSheet(); - switch errorPay to use error instead

[next thunder]

Ahh

[solid rampart]

similarly for if(errorPay){ - use error

[next thunder]

that is right

      const {  error: errorPay } = await presentPaymentSheet();

I had error defined in a previous function above

I was missing this

Thank you 🤦‍♂️

[solid rampart]

happy to have been able to help!