#mrdanvant
1 messages · Page 1 of 1 (latest)
@frosty hollow it looks like stripe is activating apple and google pay even though settings have not been applied and we have not varified our domain?
so customers are checking out with apple or google page and it is not responding as it should, resulting in duplicate payments
so your customers see Google/Apple Pay, but you don't want them to appear?
how are you accepting payments? Checkout Session, Payment Element, something else?
we redirect people to your hosted payment pages
but remember we are using stripe connect, so payments are made on our clients accounts that we collect applications fees from
we redirect people to your hosted payment pages
which one? Checkout Session, Payment Links, Hosted Invoice Page?
can you share any relevant object IDs?
i think it is check out session
let me see if i can find an iD for you
pi_3OdKSKI6Iuq9amAD156YlvYL
indeed that's a Checkout Session
so what exactly is there issue here? That Google/Apple pay shouldn't appear?
yes, because it is a connect account we do not have access to apply setting to verify our domain in their account... I am a little confused why stripe would show the Google/Apply pay if the domain has not been verified
there's no domain verification needed in this case, since it's a Stripe hosted page.
ah ok, i did wonder if that was the case... pitty your normal stripe support team do not know this...
and you can enable/disable payment methods for you connected account here: https://dashboard.stripe.com/settings/payment_methods/connected_accounts?config_id=pmc_1OeboJARhzJiqk7M9Lxh3X4K
do we need to apply anything in our code to handle payments made by Google/Apple pay?
no, it should just works out of the box with Checkout Session.
we are seeing a higher than normal number of duplicate payments becuase people think the 1st payment failed when using a google/apple pay
why would users think the payment failed exactly?
the link you sent me it very interesting... if i turn off by default the setting for Apple Pay and Google pay, this will automatically stop those from showing on my clients connected payment pages
I dont know, it is just the emails we get from purchase saying they thought the payment had failed
who sends that email? yourself or Stripe?
No, the customer is contacting us and asking for a refund as they ended up paying twice
got it, but why would customer think the payment failed? once the Checkout Session is succeeded, Stripe automatically redirects to your success_url where you can display a success message.
so there may be an issue in your implementation?
i tried applying the settings but it said i could not do it as I am not using automatic payment method
i think the issue is they are not being redirected back
i tried applying the settings but it said i could not do it as I am not using automatic payment method
got it. so you may want to change your integration to use automatic payment method. otherwise you'll need to ask your connected accout to directly make the change on their end
i think the issue is they are not being redirected back
that's not really possible. if the payment is successful, Stripe will automatically redirect them to thesuccess_url.
but the question is what do you show users on the success_url?
we are in the process of developing a new update, so we will make sure we implement this in the new update
can you please send me the best link i can give to my developers so i can make sure they are implementing the latest and best code for connect account checkout sessions to your hosted pages
do you want Direct Charge or Destination Charges or Separate Charges & Transfers? https://stripe.com/docs/connect/charges
i think we currently use a direct charge
we don't have a guide for Checkout Session with Direct Charges.
But here's the regular Checkout Session guide: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout
then make sure to use the Stripe-Account header for a Direct Charge: https://stripe.com/docs/connect/authentication
ok and does this document include coding for the payment element automatic settings you sent earlier
the only think you need to change in your current integration to use automatic payment method is to remove this line when creating Checkout Session
payment_method_types: [ "card" ]
yes but at the moment when i change the settings it will not apply them to the payment as it says we are not using automatic payment method
yep I understood. and to avoid this you can simply remove payment_method_types: [ "card" ] from your code.
happy to help 🙂