#polyscone_api

1 messages · Page 1 of 1 (latest)

steady ivyBOT
#

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

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

hallow compass
#

Since I can type more here now...

I was also just wondering, is there a way to finalise an invoice such that the payment intent will be created with automatic payment methods?

If so, would that solve this issue?

strong belfry
#

hello! gimme a few minutes to think about this!

hallow compass
#

Thanks
I can share relevant code if needed

strong belfry
#

hmmmm, do you need to have dynamic payment methods (where Stripe determines the payment method automatically)?

The only way for it to work with the deferred intent flow is if you explicitly define the payment_method_types when initializing the Payment Element (deferred flow) in options, and when creating the Invoice.

#

i haven't actually tested what i said above, but logically, it should work

hallow compass
#

Dynamic payment methods would be ideal, but if there's no way to do that with invoices in a deferred intent flow then that's ok, I can specify the method types instead

I assume then it's not possible to specify the payment intent should be created with automatic_payment_methods[enabled] from an invoice then?

And since I can't see it in the API docs I also assume it's not possible for me to just create an intent and attach it to an invoice at finalisation time?

strong belfry
#

maybe try it out and verify if it works first if you already have an example running

hallow compass
#

Ok, I'll give it a try explicitly defining the payment method types

Quick question about the payment method types
If I specify a range of method types that I'm willing to accept, would I be correct in assuming that Stripe will only show types that are applicable to the person filling in the form?
For example, if I specify konbini, would Stripe hide that option for users not paying in Japan?

strong belfry
#

aha, no, that's the problem with explicitly defining the payment method types. You need to know what's the applicable payment method types for the currency. Stripe will return an error if you try to use a payment method that does not support a specific currency.

hallow compass
#

Ok, that makes sense -- I did think it would be a little too convenient that way 😛
As long as Stripe throws an error at least I can easily catch it during testing though
I'll give the payment method types thing a try and report back if I haven't left the thread idle for too long
Thanks for the help so far

#

It does seem to work now that I've specified the payment method types
Thanks for the help

Last question, if that's ok
You wouldn't happen to know if there's a list of supported payment method types for each currency anywhere, would you?

strong belfry
hallow compass
#

Ah, thank you so much 🙂
Thanks for all of your help, it's much appreciated
Is there a way I can close thread, or mark it as complete, or should I just let it close through idle time?

strong belfry
#

you're welcome! you don't have to do anything about the thread, we'll close it after a while