#nickdnk_error
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/1313899053381189765
๐ 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.
- nickdnk_error, 21 hours ago, 7 messages
Their dash looks like this
This is account acct_1QSJRoHFgLF3ie5H
It also says Payments will be "paused soon" but their dash is not asking them to submit any information or take any action, it just says "Your account is now active!"
The account uses the exact same flow (and hence code) as all our other connected accounts which work fine with mobilepay
Hi ๐ looking at the request.
Thanks
Also we have this showing on our conenct
but when we send rthe user to the "status link" (request from account button), they see this page:
so what are they supposed to do?
Hm, it looks like mobile pay is enabled based on what I'm seeing too.
This is a terrible UX for them ๐
I'm not too sure on the onboarding part, does the Account object have anything in the requirements hash?
(we don't know the dashboard side of flows too well)
Not sure how to easily check that
It's kind of weird we have this ominous message and a "0 dkk" limit but no way to resolve it
Could there be a delay before MobilePay becomes available?
I'd suggest speaking to our support team about the outstanding piece of information if you're trying to handle it from the dashboard.
https://support.stripe.com/?contact=true
Not sure about mobilepay yet, got pulled away by the onboarding questions.
They're going to send me into a 48 hour email thread ๐ฆ
Okay you look into MobilePay, I ask support about onboarding
Ah, did you request the mobilepay_payments Capability for the Connected Account?
https://docs.stripe.com/api/accounts/update#update_account-capabilities-mobilepay_payments
uh no, I never did this
I've never done it for any account
but I can access their dash and enable MobilePay
This is their dash
Yeah, it can be requested through the dashboard as well, I think (again, less familiar with those side of things).
I think this mainly applies to dashboard-less integrations
As it also says "Required when account.controller.stripe_dashboard.type is none, which includes Custom accounts."
But I've never made this request for any account
Because you're using Standard Connected Accounts, so typically they enable their payment methods on their own through their Stripe dashboard.
The URL provided in the error message can be given to the owner of the Connected Account as it links to the correct page for requesting new capabilities.
We've never done this though
I can enable payment methods on their connected account
but let me check
is it the request_log_url param?
Enabling the Payment Method type for use with Dynamic Payment Methods is not the same as requesting the capability to be able to process payments using that type of payment method. Sometimes they're requesting automatically, but I'm not exactly sure when they aren't.
Not seeing anytrthing that looks like what you're describing
{
"error": {
"code": "payment_intent_invalid_parameter",
"doc_url": "https://stripe.com/docs/error-codes/payment-intent-invalid-parameter",
"message": "The payment method type \"mobilepay\" is invalid. Please ensure the provided type is activated in your dashboard (https://dashboard.stripe.com/account/payments/settings) and your account is enabled for any preview features that you are trying to use.",
"param": "payment_method_types",
"request_log_url": "https://dashboard.stripe.com/acct_1QSJRoHFgLF3ie5H/logs/req_qFA2aABqmsBYB4?t=1733328613",
"type": "invalid_request_error"
}
}
Was it this error you meant?
message: "The payment method type \"mobilepay\" is invalid. Please ensure the provided type is activated in your dashboard (https://dashboard.stripe.com/account/payments/settings) and your account is enabled for any preview features that you are trying to use.",
https://dashboard.stripe.com/account/payments/settings
that URL. Do you see it taking you to a page where you can request access to eligible payment method types?
Ah
Sorry I though you meant a specific link for this payment method in general
Hold on
I would normally write to my MobilePay contact to enable access to MobilePay when it was in beta
But the emails now bounce, so I don't know who to contact about this
And it is my understanding it is no longer in beta
I see the mobilepay capability was requested recently, Did that cause the error to subside?
I thinnk so yea
They say it works now
I'm just a little confused what the purpose of my connect dashboard is then
where I can enable payment methods for connected accounts
That's for enabling them for use with Dynamic Payment Methods, which isn't relevant since you're manually specifying payment_method_types.
https://docs.stripe.com/connect/dynamic-payment-methods?connect-payment-integration-type=payment&connect-charge-type=direct&connect-dashboard-type=full&on-behalf-of=false
ahh
Okay, so because these payment methods were previously enabled by my MobilePay stripe contact during the beta, we never had to do this before
So lets circle back. I suppose this means I have to integrate those capabilities into my Connect flow?
These ones, I mean
Hello! I'm taking over and catching up...
No problem
Yep, that's correct. See here for specific details: https://docs.stripe.com/payments/mobilepay#enable-mobilepay-for-connected-accounts
Okay, sorry, I didn't really follow documentaiton evolution on this since it just worked (I thought) after the beta ended
But we probably didn't onboard new accounts that wanted to use this method since it ended
The main thing is to check your connected accounts to see if the mobilepay_payments capability is active or not. If it's not, you need to request it on that account using the API.
Yea, sure, what I'm saying is this an entirely new thing we never did
But I'll add it to our connect flow for eligible accounts
I can't speak to what you did or did not do prior, or what happened in the beta, I can only tell you what you need to do now. ๐
Yes, I understand, I'm just explaining why I didn't RTFM about this