#m4tr1ck_api

1 messages · Page 1 of 1 (latest)

errant phoenixBOT
#

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

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

hexed wharf
#

More information: We try to map the invoice with the payment_intent to couple the invoice with the correct payment inside of stripe which will help with lookup. Is there any other way to achieve this behavior?
In the first tries we implemented the paymentIntent and confirmed it. It was successful and we than could create the invoice and marked it as paid_out_of_bound and added the a metadata on the paymentIntent and the invoice. But is there any way to bind both?

errant phoenixBOT
surreal moss
#

👋 happy to help

#

you're using the deferred flow right?

#

you just need to pass the payment method types to the PaymentElement and that should solve the issue for you

hexed wharf
#

Yes we use the deffered flow.

Thanks for the tip. It worked with setting the types inside the paymentElement. 😃 👍

surreal moss
#

I think a better way of handling this is to create a Payment Method Configuration

#

and use the pmc_xxxx ID both when creating the invoice and with the PaymentElement

hexed wharf
#

One little question to the deferred flow of the invoice.
If there is a paymentIntent linked to the invoice after finalizing it. Can I update the invoice to auto_advance => true to get the automatic handling of failed payments?

surreal moss
hexed wharf