#stripe_connect_platform

1 messages · Page 1 of 1 (latest)

zenith jackalBOT
fluid maple
#

koopajah fielded this yesterday

stone zealot
#

Not sure what your question is.

#

Can you elaborate?

fluid maple
#

we checked a box so that when we make payment link for a connected account that it only uses payment methods allowed on the connected account.

#

*How to remove Google Pay from that payment link

#

Google Pay is a payment method that is NOT enabled in that connected account!!!!!!!!!!!!!!!

#

But it is appearing and I have been trying to work with you to understand why payment methods that are disabled can be appearing on Stripe Checkout

#

Answer was that there was some new meta setting where we have to decide in the platform account whether or not OUR payment methods (of the platform) define the payment methods on the Payment Link OR if the connected Stripe account's enabled payment methods define what is allowed. This was new to me. So I checked a box to say that the payment methods of the connected account should govern not my platform.

#

But there is the link

#

And there is Google Pay on the Checkout Session

#

And that account has disabled Google Pay

#

But there it is

#

I checked that box and now it is 24 hours later. I was hoping now that we checked that box, Google Pay would disappear from the Checkout Session since the connect account does not have that as an enabled payment method.

stone zealot
#

How are you creating the Payment Link?

fluid maple
#

ugh

#

via the Payment Link API

#

ugh b/c I have typed this answer now for 3 days

#

Payment Link API for a connected account

#

Can you not see that on your end via the payment link i sent to you?

stone zealot
#

"ugh" isn't helpful. It just buries the important info that we need to help you in a longer thread, so I'd suggest focusing on the problem.

The Payment Link you created accepts cards and your platform and Connect settings have Google Pay on by default, so I'm not really sure why you're expecting Google Pay not to show up.

fluid maple
#

The connected account chooses payment methods

#

The payment methods they choose should govern what appears on their payment links

#

I have a separate standard account

#

I have my own payment methods to run my platform

#

There is no reason that the payment methods I like for my business should govern what my customers can do.

#

Everything should be set up in the way i described above

#

I thought this was always the case until yesterday when koopajah directed me to a page where I can set whether or not I want MY settings or THEIR setting to govern their payment buttons.

#

I want THEIR settings to govern THEIR payment buttons.

#

I thought this is now the case

#

But there is Google Pay, something not allowed by the customer appearing on a Payment Link created by the customer via our app UI via the Payment Link API.

#

Ugh because my customers will have a hard enough time setting payment methods. Now there is a dropdown of multiple categories of payment methods. I didn

#

I didn't realize that was going to be added when I checked the box. I thought it was just something I set in the platform account and didn't realize now I have to explain this extra layer to connected accounts. We don't really need that dropdown* to be added for our connected accounts. When I checked the box, you had me answer like 5 pages of questions and define our strategy. In our strategy, our connect customers don't need a dropdown since we just use their existing payment methods.

#

in theory

#

but in. actuality Google Pay is appearing even though the account disabled it...??? That is what keeps bringing me back to ask why this is happening and how we can let customers make Payment Links with only the payment methods they want and which they enable in their own account.

#

Maybe our settings are not retroactive? And we need to create a new Payment Link now?

#

But case in point is that one link where Google Pay is appearing and I want it to not. Are you still there?

stone zealot
#

I think you might be misunderstanding. As far as I can tell, the Connect account (acct_1JOWhKGkntF0z1iA) has Google Pay turned on (see screenshot) for payments related to your platform (acct_183tJHHnzkM7EAuH)

fluid maple
#

Is there a way

stone zealot
#

Which means this is working as intended

fluid maple
#

So dropdown magically appeared this morning

#

That dropdown does not make sense for our strategy at all

#

I imagine that dropdown is appearing b/c yesterday I checked this box per your team, no?

#

My customers do not need a dropdown like that.

soft cliff
#

Perhaps the confusion is you are using Standard Accounts - which are a fully capable independent Accounts with a connection to your platform - they have considerable control over their account choices...

fluid maple
#

YES!!!!!!!!!!!!!!!!!!!!

#

fully capable independent Accounts with a connection to your platform

#

yes! exactly

soft cliff
#

If you do not WANT them to be so independent... well, don't use that type of account...

fluid maple
#

but for some reason you updated Stripe to force my payment methods to override theirs. BUT as you say they should be fully capable independent Accounts with a connection to your platform

soft cliff
#

Well, "I" didn't, since I don't work for Stripe - just offering some insight...

fluid maple
#

My customers would never choose our app from the dropdown. It makes no sense for them. They are full capable independent accounts

#

GigStartr. Please don't

#

OK, so Stripe seems to have spun up a page of payment methods settings somehow in duplicate for our connected accounts. Guys, you are going to put us out of business with the endless - no communication to us ever gotcha wild updates that totally change our business. 😦

#

I don't even understand what it is you are doing here and it affects all of our connected accounts.

#

I don't know what to tell a customer to have set here. Our customers are standard Stripe accounts and should be independent and I think that dropdown which I currently don't even understand is going to confuse the heck out of them