#warhost_error

1 messages ¡ Page 1 of 1 (latest)

onyx cometBOT
#

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

📝 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.

clear atlas
#

hi! then the only way is to pass payment_method_types=>["sepa_debit"] when creating the Intent in PHP, so it matches the frontend.

cinder storm
#

I had that before. The issue I have with that is it's making it harder for me to know when to create an order in my online-shop for that payment.
Basically I was creating an order with status unpaid, then Stripe Elements does it's stuff and then it relies on a redirect/webhook to update the status.

#

But I don't follow why this is not possible with manual payment methods, seems weird.

clear atlas
#

not sure what you mean, it is possible(you just pass payment_method_types on the front and back end and use that confirmationToken integration the same way otherwise).

cinder storm
#

oh I'm so sorry! I misread totally

#

I thought I had to go back to creating the intent first, pardon me.

#

Yes that works! Thank you!

#

10/10 ⭐

clear atlas
#

awesome!