#nick_connect-pmc

1 messages ยท Page 1 of 1 (latest)

vague skyBOT
#

๐Ÿ‘‹ 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/1485663786600894575

๐Ÿ“ 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.

silent wadi
#

This is from a platform perspective. I am managing payment methods/capabilities for Standard Connect accounts

dull scarab
#

Hello, looking in to this

dull scarab
#

Yep the dashboard setting should turn that capability for existing and new accounts. So you shouldn't need to keep explicitly specifying it

silent wadi
#

Alright, so I can take out that API call entirely

#

Regarding the payment methods and how they are managed from the platform: It seems the connected account users cannot select which payment methods they can accept via our platform (it just says managed by <platform>), so can I somehow provide my own per-account configuration of payment methods?

vague skyBOT
silent wadi
#

It looks like I can only set it on/off for all connected accounts via my dashboard, not for individual accounts. My case is that some payment methods may not be relevant for some connected accounts (for instance, some have high fees and may not be desired)

dire dock
#

nick_connect-pmc

silent wadi
#

Ah, I was missing the checkmark for "allow connected accounts to customize"

dire dock
#

gotcha

silent wadi
#

So followup question. If for instance I have a payment method where I have X number of "eligible" in the column, and I just set it to "on by default", will it then just enable it automatically, or do I need to do anything else via the API - I mean; does it apply retroactively or is it the default set applied when accounts are connected?

And if I wanted to manage this from the platform, all I would need was to list the paymentMethodConfigurations in that account's context and update the default one accordingly, yes?

dire dock
#

"it depends" is the sad answer. Depends on the type of connected accounts, how they were created etc. I honestly barely understand this. It can automatically propagate so the easiest is likely to do the Dashboard flow first and check back tomorrow if it's enabled or not (it's done slowly by a background job) and if not you can enable it yourself via the API (or the Dashboard UI)

silent wadi
#

Yea it's not the most intuitive setup I've seen, since it has so many layers based on context (platform vs connect, default vs non default)

dire dock
#

agreed, it's baffling to me every time I look especially as most of it only works well in Live mode

silent wadi
#

I am leaning towards building it on our end and using the API, but of course, that takes some time and I need it to work Now(tm). If I let users manage the payment methods via their own dashboard now (after I checked the box to allow), and I then create an API integration on our end later, then that's going to edit the same list, right? I mean, if I implement it correctly and use the default one, of course. I just want to make sure I am reading/writing to where I think I am.

#

(all accounts are standard connect)

dire dock
#

yes

silent wadi
#

Good, beause then I can direct users to their Stripe dashboard for now and build this later

dire dock
silent wadi
#

Yea, I like those, but unfortunately they don't work well with Standard Connect (at least they didnt last time I looked) because you need to authorize/log in on the component in that case

dire dock
#

agreed, I wish the docs were clearer on which type support those (though we also removed account types so ยฏ_(ใƒ„)_/ยฏ)

silent wadi
#

It says when I save the payment methods, that it will not "request capabilities for accounts" - which implies that I actually do need to make the API call I'm currently making (initial question).

#

I do this when a connect account is connected that should have MobilePay:

$client->accounts->updateCapability($stripeUserID, 'mobilepay_payments', [
    'requested' => true
]);
#

It's "capability" vs "payment method enabled" that's tripping me up here

dire dock
#

I thought you couldn't control Capabilities on Standard connected accounts though

silent wadi
dire dock
#

so yeah maybe you have to. The tool implies that it can request the Capabilities in the Dashboard but I think it depends if extra information is needed. Sorry I wish I had a better answer, it just makes no sense every time I look at it

silent wadi
#

Or the API succeeds without error ๐Ÿ˜„

#

Yea, I'm a little lost too. It's pretty confusing to users, because under our application's default payment method (see pmc_1PLwmTJR7gx5Fovj9OOneNQO for instance), it lists Apple Pay as "reqeuires action" which it most definitely does not for them. It works because I add the domain in the connect flow via API; but this isn't visible anywhere on their dashbord (we talked about this for).

dire dock
#

agreed, the whole thing is full of quirks that make no sense to me. I flagged feedback for years ๐Ÿ™

silent wadi
#

I'm unsure how to proceed, honestly. It seems like building my own API integration and have users never touch their own Stripe dashboard is definitely the way to go, because anyone who isn't a Stripe power user (whic means 100% of my user base) will have no chance at all to figure this out

dire dock
#

My understanding is when users turn the feature on in the Dashboard it will request the Capability, so I still think sending them to the Dashboard is the right approach for now

silent wadi
#

Klarna is enabled and works for this account. This message is going to send everyone down a completely wrong path and give the indication that Klarna isn't available to them.

Screenshot_2026-03-23_at_17.44.24.png
silent wadi
dire dock
#

yeah that's fair

silent wadi
dire dock
#

maybe it doesn't ask that?

#

Sorry again I wish I had a better answer, but you should be able to confirm quickly with what one of your connected accounts sees in the Dashboard in Live mode

silent wadi
#

This is live mode dashboard screenshot

#

For a connected account that can accept Klarna via our application

dire dock
#

but your own, or the connected account's? Which exact view are you in? Sorry truncated screenshots so really hard to say

silent wadi
#

Their dashboard, where they enable their payment methods

#

(like I just allowed them to via the checkmark i was missing)

dire dock
#

gotcha. So yeah fair feedback that this likely should be hidden for the Connect platform's PMC config or have a clear "talk to your platform".

silent wadi
#

Yes, something needs to change or be added here because this is going to make a user try to add their own domain (which doesn't make any sense)

#

it also implies it isn't working, which it is

#

just for full context, I do this "for them" via API when they connect to our application, which isn't visible anywhere on the dashboard as far as I can tell

$client->paymentMethodDomains->create(
    [
        'domain_name' => 'our ticketing domain goes here',
        'enabled'     => true
    ],
    ['stripe_account' => $stripeUserID]
);
dire dock
#

To be clear: nothing will change. I'll give the feedback but it won't happen. At least not any time soon

silent wadi
#

I sense this is not a product you are involved in ๐Ÿ˜„

dire dock
#

I wish. I have like 15 jiras in the backlog ๐Ÿ™

#

I will give the feedback, I'm just trying to set your expectations on that one

silent wadi
#

Sure. I'll work around it for now

#

To make it even worse, it seems my application has a separate PMC for "billing" (which I did not create)

#

(not expecting you to do anything about this)

dire dock
#

yeah that one is because we used to have a setting for Invoices payment method types for many years and they often differed so we had to "split them". It's a mess, I guess you can tell how annoyed I am at all of this ๐Ÿ˜“

silent wadi
#

can I delete that somehow? That would at least make it easier for me to explain where to send users (go to dashboard, payment methods ,select Nyx account, disable payment method X)

dire dock
#

I don't know either ๐Ÿ™

silent wadi
#

Alright. I guess I have to not link to this at all then and tell them to contact our support and we'll have to help them navigate this if they want to enable or disable a payment method, until I can build something on our end to manage this via API.

silent wadi
dire dock
#

yeah fair. I'll still file the feedback so if you want to write in I can link to 2 together

silent wadi
#

Not right now, maybe i'll get back to it later. If you say it's essentially a waste of time, I don't want to write it all up again

#

Here's an actual bug though you can take if you want. Supposed to be just one row per country. This is under Settings -> Connect -> Payment methods and then the Bank transfer PM. The others don't look like this.

Screenshot_2026-03-23_at_18.14.57.png
vague skyBOT
dire dock
#

ack I'll add this to the long list of jiras for this thread, will file them all today

silent wadi
#

I can disable the billing one on my end, by the way!

Screenshot_2026-03-23_at_18.18.52.png
dire dock
#

but if you disable it, does it use the main one for Billing" That's the part I have no idea about lol

#

and yeah exactly

#

brand new accounts would have just one I think

silent wadi
#

But why would my own account use it? It's a connected config

Screenshot_2026-03-23_at_18.21.44.png
#

mine has a different ID

dire dock
#

I don't know what your words mean

silent wadi
dire dock
#

we created one for each connected account to mirror their own Dashboard settings for Invoices which is what was used for all Subscriptions for their own and the ones your platform created for years

silent wadi
#

(they are not the same PMC ID)

dire dock
#

no

#

Sorry it's really complex. Connected account A has pmc_123 for their own integration, then pmc_ABC controlled by your platform for your own integration for payments and pmc_XYZ called "Billing Payments" that is specific to Billing (Subscription and Invoices)

silent wadi
#

It is ๐Ÿ˜„

So when I try to delete "Billing payments" under "connected accounts" (XYZ in your example), I would expect that to work and then my connected accounts would default to "default" for billing - but it says it's "in use" and redirects me to billing config, but for my platform, which was not what I was trying to get rid of. The idea here was to reduce the number of options for connected users when they go on their dash to configure payment methods.

But if I can't delete it, it doesn't matter anyway (and at this point we're just agreeing it's confusing with no resolution), so let's just move on

dire dock
#

๐Ÿ‘

dire dock
#

okay filed all 4 jiras so hopefully I can get you some answers in the future. You likely won't need those by then but doesn't hurt to get to the bottom of the exact flow