#juangomez0120_automatic-payment-methods-not-enabled
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/1366859964559130815
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
You seem to be creating the PaymentIntent on behalf of a Connected Account. Have you enabled ACH debit on the connected account?
I'm not explicitly specifying any payment_method_types during the creation of the PaymentIntent, so I assume that all payment methods configured in my Stripe dashboard will be considered as valid options.
Can you try passingautomatic_payment_methods: { enabled: true }}as well?
It is enabled for the connected account
I'll try the automatic_payment_methods: { enabled: true }}
Thanks!
Hey! Unforunately, this didn't work either
I was able to reproduce the problem localy on the test environment
The PaymentMethod provided (us_bank_account) is not allowed for this PaymentIntent. Please attach a PaymentMethod of one of the following types: card, link. Alternatively, update the allowed payment_method_types for this PaymentIntent to include "us_bank_account".
RequestID: req_gAzb5yuJ4SwIvX
This is the body I'm sending to the API:
payment_intent_data { amount: 2350, application_fee_amount: 258, currency: 'usd', customer: 'cus_SBzdyE23yTxJDj', description: 'Order #1980 - 1x Location Class Test, 1x Location Class Test at 9:00am Tue, Jun 17 CST', metadata: { TaxAmount: 92, pendingOrderId: 'Pyncpa88MKNhmPxrXs7JW2XB_1745956516', pendingOrderCollection: 'ordersPending', partnerId: 'yAzyLUwjUQcnR9lau7QdGqGN9IU2', stripeAccountId: 'acct_1PxYVqPWe2hFzQFz', franchiseFeeAmount: 0, migrationId: undefined, pendingClassExperienceType: 'Class', pendingClassId: '8F6Ne6krhspG7m5uXRO0' }, setup_future_usage: 'off_session', automatic_payment_methods: { enabled: true }, payment_method: 'pm_1RJKFCBsYzIqHjobZSUvtJRE' }
Hi, taking over as my teammate needs to step away. Let me catch up.
Cool, thank you
It looks like you're using OnBehalfOf: https://dashboard.stripe.com/test/logs/req_gAzb5yuJ4SwIvX
This typically happens as we're looking at the connect accounts settings
1/ You need to turn that payment methof on the connected accounts which you said you did
2/ The connected account needs to have the right Capability requested, https://docs.stripe.com/api/accounts/object#account_object-capabilities-us_bank_account_ach_payments
It looks like when you created the account, you only passed in card and transfers: https://dashboard.stripe.com/test/logs/req_Jvox2VTAw9X9sK
1/ You need to turn that payment methof on the connected accounts which you said you did
- Yes it is turned on
2/ The connected account needs to have the right Capability requested, https://docs.stripe.com/api/accounts/object#account_object-capabilities-us_bank_account_ach_payments - I'll take a look at the account object to search for that attribute
But in the meantime, using the test account in the test environment throws the same error, and that account isn't a connected account
Oh nvm, I understand your point now. Let me check and I'll get back to you, thanks!
The connected account that payment was onBehalfOf does have the ach payment enabled
I haven't tested the onbehalf payment with the automatic_payment_methods: { enabled: true } attribute tho. I'll enable those payment methods in my test account and test again. If everything works correctly I think we are good to go then
Let me know what you see after testing
How exactly can I enable this on my test account? I thought it was via the payment methods setting page but it doesn't seem to change. Do I need to do this strictly via the api?
I do not have expertise on the Dashboard and we're here to help with API/ Integration related issues. I think you could update the Connect Payment Method Settings
Yeah that seems to be it! Thanks! It's still updating the information, it takes some time, I'll let you know when it's done so that I can run the test again
Sure thing!
Hey! It's working correctly!
What's weird is that I've also tested the flow by removing the automatic_payment_methods: { enabled: true } and the payment intent was still confirmed correctly, which makes me think that the problem doesn't come from that attribute
Yeap, depending on the API version you use, we default to the automatic payment methods
Glad it is working now!
But then this means that we still have a problem with the production case I sent you earlier today:
Request id: req_Q73GszXPLem2dS
OnBehalfOf: acct_1QQU6SB9Nm6MrCgU
Who has all the capabilities show in the image
And also has the payment method configured in the payment method settings page
Is there any way you can point me to the payment intent object that's related to that request? So that way I can see if maybe I'm sending the incorrect paramenters
Did you try this payment after you both enabled and added the capabilities on that account?
How are you initializing the Elements? It looks like you're using https://docs.stripe.com/payments/accept-a-payment-deferred flow to collect payment method details, then create the Intent by passing that payment method
The account always had the capabilities. The test account was the one that didn't. The one I've just shared have always had the capabilities
You mean client side? I use the react-stripe-js library. I use the <Elements /> component as a wrapper for the other payment element components, that also come from the react-stripe-js library
I send a request from the client to my backend with the selected payment method id. I then process in the backend the payment intent creation using the payment method id I send from the client
Hi hi! Iโm going to be taking over for my colleague here. Give me a minute to read back and understand things.
Still digging. I haven't found the source of the issue yet.
It's okay. I have more cases if they might be helpfull, this actually happens a lot to us
Yes, if you have an example from a different Connected Account that'd be great.
Actually, it looks like you need to add automatic_payment_methods.enabled=true to your call to create the Payment Intent in order for it to pull in the Payment Configuration.
(...which should then allow these to work)
req_fQfOfzR6be7CfM
req_3VAlm6dLZwrNfZ
req_HL4hln58KKMmw9
req_w9K7aDwtmZDsNv
req_kzAbhSmRszBWbK
Here are five different examples for the same error message
Is this a thing only for connected accounts? I tested this today with a test account and the payment with a bank account went through even if I didn't had that property added in the request
I don't have a bank account to test this in production with a connected account unfortunately
Those are all missing that parameter, so they're seeing the same error.
Okay, I'll add the parameter then! Thank you
Of course! If you run into more issues with this, or with anything else, don't hesitate to pop in and ask! ๐
Thank you! I've been facing the exact same problem with the link payment method as well, no connected account payment also
req_doNbWbfmolIBAD here's an example
Is this caused because of the same reason?
That's a Connect charge.
How can you tell if it doesn't have the onBehalfOf property?
I have internal tools that tell me - and yes, this is most likely the exact same cause.
Okay cool, thank you very much!
juangomez0120_automatic-payment-methods-not-enabled