#danielncr_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1270157749199568937
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
I see the only payment method type available is card. What other payment methods are showing up?
cash app and us bank accounts
Do you have an example where I can see this rendered?
Sorry but this is a screenshot and it doesn't give me what I need. Can you provide a publicly accessible URL where I can observer this myself?
well, you'd have to fill out the form first to get to the payment modal, but here: https://tytowing-llc.fundjournalism.org/donate/
Hmmmm... I only see the Card input
that would happen if you selected one-time -- try monthly
Are you using the deferred intent flow or are you creating a payment intent prior to rendering the Payment Element?
One-time payment, same UI
right, it works for one-time but fails for monthly
I have not been able to reproduce seeing any payment method types besides cards
did you try monthly?
That is the first sceenshot I shared, you can see the text in the button
because I can reliably reproduce it in an incognito window with either monthly or yearly
Are you creating a payment intent when that loads?
yes,
I"ve tried every single option and I cannot see any payment method type but card
yes
Can you share a payment intent ID that corresponds to this?
Wait. The UI I'm interacting with is rendering using Setup Intents
It seems like we are not interacting with the same code
yours got flagged by our fraud detection - we use setup intents to quarantine suspicious contributions
bufo.io isn't a valid email domain ๐
Well, the Setup Intent is configured with the same payment method types and all I see is a a Card input. I'm still not sure how you are seeing other PMTs but I'd need to see that UI in my own browser to dig further.
Can you try again with inputs that don't look as fraudulent?
I did using an @google.com email, still no joy
ok, give me a sec
ok if you now use judith.wombat@bufo.io it should not get flagged as fraud
Okay now I do see the extra payment methods
Let do a little digging
These payment intents are being created through a Subscription. Here is the request
https://dashboard.stripe.com/logs/req_3MWz637spTkAYx
When I look at the underlying Payment Intent (pi_3PkaWQPft6gAiWoq0oaDb30P), I see the following
payment_method_types: [
"card",
"cashapp",
"us_bank_account"
],
This is what determines what will be displayed in the Payment Element
but we're not setting that in our code afaict
I suspect the issue here is that the Payment Method Types allowed for Invoices is specified in a different part of the Dashboard, here https://dashboard.stripe.com/settings/billing/invoice
This is really easy to miss to here is where you need to check
that's on the account itself, right? Is there a way to do this on the platform/connect account?
This is my own account, I just mocked it up.
(and yes, I had no idea there were separate settings for invoices)
Yeah, honestly I find this design choice very frustrating but enough big users wanted separate Invoicing controls
but we're using Connect -- so is there an equivalent Connect setting?
(as setting it on each individual account would require access that I don't think we have to the connected (Standard) accounts.)
(and it would also be a pain)
or can we override this in code?
- You can override this with code when you create the Subscription. The parameter is
payment_settings.payment_method_types
https://docs.stripe.com/api/subscriptions/create#create_subscription-payment_settings-payment_method_types
And do you want to specify Cards as the only PMT for your Connected Accounts or including your Platform Account?
We'd like to specify cards as the only payment option for connected accounts.
Because your settings govern what the Connected Account Invoice template is set to. When I log in to the Connected account's dashboard, I can't even see the Invoice settings
Right -- I have access to both the platform and this particular connected account.
but are you saying that if I change the invoice settings for my platform account it will apply to my connected accounts as well?
you can customize payment method configurations to apply to Connect accounts only. But I want to check to see if this impacts Invoice settings as well
https://docs.stripe.com/connect/multiple-payment-method-configurations
yeah, I guess I assumed when we blocked something here that it would apply to invoices on connected accounts, but that doesn't seem to be the case: https://dashboard.stripe.com/settings/payment_methods/connected_accounts?config_id=pmc_1Pe3FUBMAMOLTEak6Zm4Kx0F
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
I see cash_app and us_bank_account are off but this isn't apparently reflected in the Invoice settings.
well, just for fun I just disabled cash app in the platform account invoice settings and it didn't remove it from the payment method modal
so, I guess what I'm hearing is that we have to set it via the API and the platform payment method settings won't apply to subscriptions on connected accounts?
๐ Taking over this thread, catching up now
thanks
The Payment Method Configurations API doesn't apply the payment method settings of the invoices
You'd need to specify payment_method_types for the invoices
If the payment_method_types is not specified, it will take the payment method settings on invoice settings of the connected accounts, which this setting can't be controlled by API
okay, thanks.