#nyxi_paymentmethod-multibanco
languid ibexBOT
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.
- nyxi_docs, 1 day ago, 24 messages
- nyxi_paymentelement-updates, 1 day ago, 37 messages
- nyxi_automatic-payment-methods, 1 day ago, 91 messages
- nyxi_docs, 5 days ago, 11 messages
- nyxi_pi-autopms, 6 days ago, 62 messages
- nyxi_invoice-return-url, 6 days ago, 79 messages
zenith quiverBOT
đ 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/1245511583799578625
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sullen cliff
Multibanco is only supported on Sources today. We're literally working on the GA of PaymentMethod soon though
nyxi_paymentmethod-multibanco
lament locust
Okay, cool. Just wanted to check.
sullen cliff
so it works, but via the old Source integration (which is supported but undocumented). If you don't yet support it, I'd say ignore it until we release it on PaymentMethod
lament locust
I'm currently migrating everything to the automatic_payment_methods logic, and we did have interest from Portugal for our product, so it may be relevant soon. I assume that when it becomes available in this context, I just won't have to change anything?
The reason I came across it here is because I'm writing some code that will turn the payment_method_details object into a common interfaced object (type, payment identifier, last4 and card brand, where applicable), and multibanco was the only payment method that did not have a constant in the PHP library, hence why I thought it was an oversight.
i.e. this
switching on this value in this code, where it does exist, apparently: https://docs.stripe.com/api/charges/object#charge_object-payment_method_details-type
sullen cliff
I just won't have to change anything?
correct, just turning on Multibanco in your Dashboard!
and yeah Multibanco is the only one still on Sources that we haven't migrated for now but the team has been working on it for the past 3 months and we're close to a GA.
lament locust
Alright. I'll just use the string value then and write a TODO.
eventually replace it
lament locust
> I just won't have to change anything?
correct, just turning on Multibanco in ...
Nice. By the way, is there a way to not include, but exclude a payment method? Currently it just defaults to "everything that's enabled" or you can provide an array of the payment methods you want. Is there a way to do the opposite?
sullen cliff
no that's not something we support today. In that case you'd do a PaymentMethodConfiguration that has all that you want enabled
lament locust
Okay, but if I provide an explicit list of enabled payment methods, in a combination that is not supported (for whatever reason, like currency), it won't error? Edit: I just understood now that PaymentMethodConfiguration is an object and not a reference to configuring the payment methods on the intent.
say if I provided USD and mobilepay and card
would it then just not allow mobilepay?
https://docs.stripe.com/connect/payment-method-configurations looks interesting though.
sullen cliff
correct it would "just work". What you do in the Dashboard by hand is basically changing your own default PaymentMethodConfiguration on your account
so if you wanted say an "all but no bank debits because it's risky" you could enable all but those and then when you create a PaymentIntent and pass payment_method_configuration: 'pmc_123' it will work and select the compatible ones (currency, amount, etc) from what's enabled on the PMC
sullen cliff
yes
sullen cliff
awesome!