#Dade-googlePay
limber halo
@rugged vine hi! can you clarify exactly what screen this is? A screenshot, and the code of what you're using? Is this about a native Android app?
rugged vine
hi, no app only payment method screen integration
and based on the UI config it should be disabled
limber halo
my guess is you're doing this on two different Stripe accounts
do you have a link to the Checkout page? Like the https://checkout.stripe.com link that you're getting that first screenshot from?
rugged vine
right i am using a link similar to what you posted
and the account is confgiured ok since all the payments land in that account
limber halo
hmm, so you're using an Express account and creating the CheckoutSession on that?
you shouldn't do that, you should use Destination charges for Express accounts https://stripe.com/docs/connect/creating-a-payments-page?platform=web&ui=checkout#destination-charges and not Direct charges. That's why this happens anyway. You are configuring the settings on your platform account, but the Express account's settings are different(and they don't have a dashboard to log into to change them and we don't have an API for it right now, so they just use the default settings(which includes Google Pay)).
rugged vine
i am not sure i follow this
so the screen i posted above takes no effect on my payment methods configuration?
aaa the payment methods config are taken from the connected express account in this case because in tha api we use stripe-account parameter?
limber halo
yes
we use stripe-account paramaneter?
that makes it a Direct Charge(which you should not really do with Express accounts, for reasons like this one)
rugged vine
in our business case it is imperative that we charge directly the connected express acount and the main account only gets the application fee
with the destination charge i can still obtain this, right?
we need direct charges, this is our business model, we are a white label platform
limber halo
how are you going to handle refunds and disputes?
(because if you use Express, remember the connected account does not have a Stripe dashboard so they can't log in to issue refunds or respond to disputes, you'd have to call the API on their behalf to do that so you need to build that into your user dashboard)
we usually recommend : Standard + Direct ; Express + Destination ; Custom + Destination
rugged vine
yes, we do a lot in our platform system, actually the only screen hosted on stripe is the payment method session
limber halo
fair enough! But yeah, if you use Direct+Express, it's not possible to configure the payment method selection in Checkout as far as I know.
rugged vine
it seems for me a bit random: on the main account i only allow card and sepa. On the connected express payment session i only see the gpay as extra. Why not alipay or ipay... or other ones
so there are some effects of the main account settings
or other way the question: how can a platform account limit the choice of payment methods for an express account?
limber halo
it seems for me a bit random: on the main account i only allow card and sepa. On...
likely those are not active on it(you have to request the capabilities for it when onboarding the account https://stripe.com/docs/connect/account-capabilities , you probably just request card_payments for example)
rugged vine
ah, in the checkout session i will have to add the 'allowed' payment methods for that session
limber halo
yes you can do that as well, pass payment_method_types, but for example iDEAL won't be an option if you don't pass ideal_payments into requested_capabilities when creating the account since the account won't be onboarded with it
rugged vine
we never used the capabilities, we did all of this setup over the UI
but to summarise our issues:
- need to check the express capabilites settings (API)
- quick solution now for remove the gpay is to pass only card and sepa to payment methods when creating the session
i think i got now, i'll let my team know