#pckzz_wallets-pmc-sessions

1 messages · Page 1 of 1 (latest)

marsh trenchBOT
#

👋 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/1467931760493985804

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

manic wyvern
#

Hi 👋

What the actual question here?

#

That GooglePay & Apple Pay aren't working?

#

Neither of the IDs you provided are complete, unfortunately. I cannot look up either the request or the payment intent

north valve
#

ids
acct_1RgapqJlze71f98o
pi_3SvTT0Jlze71f98o1P1QsGYj

The actual question: Yes – Google Pay and Apple Pay are not working.

Google Pay: elements/sessions returns google_pay_preference: "disabled", so the button never appears on Android/Desktop.

Apple Pay: The button appears on iPhone but does nothing when tapped

I’ll look up the complete req_ ID from Dashboard > Developer > Logs and the full PaymentIntent ID and send them in my next message.

I opened a ticket via email, but I prefer Discord as it’s faster

manic wyvern
#

Do you have a publicly available front-end where I could test this?

#

The payment Intent you shared failed due 3DS authentication.

#

You can see in the confirmation request that the next action property was populated with the details to trigger a 3DS authentication session

north valve
#

egarding the PaymentIntent with 3DS: we may have tested with a card that required 3DS. Do you mean our integration isn’t handling next_action/3DS correctly, or were you only describing that specific payment as failed? Card payments have been completing for us when 3DS is handled in the browser. Can you share what we should change for 3DS, if anything?

manic wyvern
#

That payment intent is in LIve mode so attempting to confirm with one of our Test 3DS card numbers would have thrown an error

north valve
#

Just to clarify: the payment error / 3DS is not the issue – that was just a test with my personal card.

The problems we need help with are:

  1. Google Pay: elements/sessions returns "google_pay_preference": "disabled" on Android/Desktop. The button never appears, even with domain registered and wallets enabled in the Dashboard.

  2. Apple Pay: The button appears on iPhone but does nothing when tapped. Possible cause: .well-known/apple-developer-merchantid-domain-association returns 404.

We're not blocked by card payments – we're blocked by these wallets not working.

manic wyvern
#

Also testing in live mode is a violation of Stripe's Terms of Service

north valve
#

Oh, sure – thanks for the heads up. We'll use test mode for future tests.

manic wyvern
#

Thanks for the URL. I'm investigating now

north valve
#

🤝

#

Add ?stripe_debug=1 in url if u need

manic wyvern
#
  1. Google pay does not require domain registration, but I also do not see it as available.
  2. Apple no longer requires the hosting of a domain-associated file
#

When I look at the logs for the session I am viewing, I see that only ⁨card⁩ and Apple Pay are considered valid.

north valve
#

For Apple Pay: if the domain-associated file is no longer required, what could cause the button to appear but not respond when tapped on iPhone? Is there something else we should check (e.g. redirect/confirm flow, ⁨return_url⁩, Safari-specific requirements)?

#

And just to confirm: is Google Pay being excluded here due to country/currency (BR/BRL) or Connect account rules? We’d like to know if there’s any way to enable it for our donors.

#

Sorry for the delay

manic wyvern
#

Okay so the Platform config has Google Pay turned off so that's the first issue.

#

But Apple Pay renders properly.

#

Which makes sense because the logs we return say only card and Apple Pay are valid options

north valve
#

It was already enabled here, or is it somewhere else?

#

I'm using OAuth Connect Stripe, where my account chooses the enabled options

manic wyvern
#

The payment method configuration used for this is ⁨pmc_1Sv4wtJlze71f98o342Gudrf⁩. It belongs to ⁨acct_1RgapqJlze71f98o⁩ and it has Google Pay turned off

north valve
#

okay, one minute

#

pmc_1Sv4wtJlze71f98o342Gudrf⁩

manic wyvern
#

Those screenshots unfortunately don't mean anything to me

north valve
#

translate:
FADE & CO AGENCIA DE MARKETING DIGITAL LTDA is managing the payment methods for you.
FADE & CO AGENCIA DE MARKETING DIGITAL LTDA has not allowed you to manage payment methods in the Dashboard.

Integration Options Manual
Check the payment methods that disable manual integration changes for use.

north valve
manic wyvern
#

Yes

#

That is the payment method configuration that is being applied when the checkout site loads

north valve
#

The configuration of pmc_1Sv4wtJlze71f98o342Gudrf (fade & co) that I sent in the image says:
FADE & CO AGENCIA DE MARKETING DIGITAL LTDA did not allow you to manage payment methods in the Dashboard.

#

However, I have access to FADE & CO, and we have this enabled here as well, see the image:

manic wyvern
#

Nope, the PMC being used belongs to Pantera Checkout

#

You are looking at the default for your platform. There is a separate PMC that applies to your Conencted Accounts

#

It's turned off there

north valve
#

Could you give me directions on where to find and enable it?

manic wyvern
#

You can see in that screenshot that you are looking at the Payment Method Configuration that ends in ⁨6vv⁩. The one being applied to your elements sessions is ⁨pmc_1Sv4wtJlze71f98o342Gudrf

#

In your payment method setttings dashboard, you should see an option to specify the PMCs that apply to your connected accounts. It should look like this:

marsh trenchBOT
#

pckzz_wallets-pmc-sessions

north valve
#

so

#

i clicked here (pmc_1Sv4wtJlze71f98o342Gudrf⁩)

#

but appears this:

#

when i click in here:

#

(pmc_1RgaqPJlze71f98oWGNZ25LO) other

#

appears this:

#

These are the only things i can change within the payment method settings

#

Please forgive me if I'm not understanding correctly.

manic wyvern
#

I'm sorry but that isn't the PMC that is being applied on the site you provided me

#

And I can't guide you through the dashboard at this point.

#

We know the issue with Google Pay not displaying is a PMC configuration issue

#

So at least you know it's not how Stripe.js is configured

north valve
#

From what I understand, the problem is pmc_1Sv4wtJlze71f98o342Gudrf, which, when I go to view the payment methods, displays the following message:
FADE & CO AGENCIA DE MARKETING DIGITAL LTDA did not allow you to manage payment methods in the Dashboard.

manic wyvern
#

Whose dashboard are you accessing?

north valve
#

from the Stripe account that I connected to the website to receive my payments.

#

acct_1RgapqJlze71f98o

marsh trenchBOT
turbid schooner
#

Hello
Stepping in as Snufkin needs to step away

#

The Payment Method Config that applies here belongs to the Platform account.

#

You'd need to login to the platform account to enable google pay on that config

north valve
#

My account (acct_1RgapqJlze71f98o) is connected to FADE & CO AGÊNCIA DE MARKETING DIGITAL LTDA.

FADE & CO AGENCIA DE MARKETING DIGITAL LTDA has these payment methods configured:

#

I'll be away for a while, but you can send me the resolution! I'll do it as soon as I get back. We can still keep in touch.

turbid schooner
#

The screenshot you've shared is not the PMC being used though

north valve
#

Logged into platform account, I have this environment:

#

ooh

#

damn

#

I think I found it.