#arden-malikb_unexpected

1 messages ยท Page 1 of 1 (latest)

mint mossBOT
#

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

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

placid star
#

๐Ÿ‘‹ happy to help

mint mossBOT
dense talon
#

Yes, we have registered the domain on both the Platform and Merchant accounts via API and through the dashboard.

#

but it's still not working. Could you provide insights on what might be causing this issue?

fossil sage
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away soon. Are you creating the Payment Intents first and using their client secret to initialize Elements, or are you creating the Payment Element first?

dense talon
#

We have just created Payment Element first then we post the data for PaymentIntent to process the request for payment

fossil sage
#

Gotcha, do you have a publicly accessible test page that you can share then so I can take a closer look?

dense talon
#

Sure , I giving that type of page where you can test it

#

Here is the URL for the checkout it enables for 19 min

fossil sage
#

Thanks, taking a look

dense talon
#

okay

fossil sage
#

Can you share the code you're using to initialize Elements? I'm asking because so far it doesn't look like this is set up as a Direct Charge style flow. Also I see this page is using a livemode publishable key, did you get this working using testmode first?

dense talon
#

Let me share the code for initialize

fossil sage
#

Are you using OAuth to onboard your Connected Accounts? (I'm trying to make sense of the keys I'm seeing in use)

#

Apple Pay is appearing as expected for me, so if you aren't seeing that it's likely because you don't have Apple Pay set up on your device, aren't using the correct browser, and/or don't already have a card in your Apple Pay wallet.

dense talon
#

Yes I said earlier the flow with Platform and Merchant account

fossil sage
dense talon
#

Ok that's my end I will check

fossil sage
dense talon
#

So what steps need to follow for this type to enable?

#

DPM

fossil sage
#

Turn it on within your Stripe dashboard, on the page I provided a link to.

dense talon
#

This is for the Google Pay but what about the other payments like crypto, pay later methods

fossil sage
#

You would turn them on using that same page. Currently you only have cards, Apple Pay, and Link enabled for your livemode Direct Charges.

dense talon
#

Ok let me check from above link

#

So there is only one issue or do we need to change our implementation/initialize?

fossil sage
#

As far as I can tell, the problem is just that neither you nor your Connected Account enabled any Payment Methods other than the three I mentioned.

#

I was asking about how you were initializing Elements because I didn't see the stripeAccount setting being used, which is how recent Connect Direct Charge flows are typically built. But that's not the case if you're using OAuth and using those keys instead of your Platform's keys.

dense talon
#

Okay mate. I got you few of your points. It means I did enabled the configuration from different payment configuration in the both account else i have enabled

#

I just need to enable this setting with this provided configuration, and I expect the enabled payment methods to be visible.

#

I see this is enable

fossil sage
#

You're not on the page I linked to it seems like, because the configuration for your Direct Charges doesn't show that Active value. Instead there will be a dropdown where you can select On by default, Off by default, or Blocked. Unless you're showing the screen from your Connected Account's point of view, but the screenshot is too cropped for me to be able to determine that.

Similar to this screenshot that we show in our guide for setting up DPM for Connect:
https://docs.stripe.com/connect/dynamic-payment-methods

dense talon
#

Ok you're correct! that from the connected account. I enabled it from the Platform account it taking time for 5-10 min

fossil sage
#

Since you let your Custom Accounts customize the payment methods offered for you integration, they can make changes to their individual settings in their own dashboard, but it didn't look like that had been done for the accunt that was being used on the site you shared.

The Connected Accounts will see multiple Payment Method Configurations in their account settings. They'll see their own, as well as the one for your Platform.

mint mossBOT
dense talon
#

We have checked for the live working example but it doesn't affect live users.

#

That is our testing account

fossil sage
#

I'm not sure what that means, you were using a livemode key on the site you shared, so that site is using your livemode settings rather than your testmode settings.

dense talon
#

Can you please check there with given above URL for the google pay?

fossil sage
#

That URL expired

hot dagger
#

Taking over here from Toby. Let me check that URL ๐Ÿ‘€

dense talon
#

Okay

hot dagger
#

Yep, I see Google Pay. If you don't then that implies a device/client issue. Does Google Pay show for you here?

Make sure your Stripe payment integration accurately renders Apple Pay and Google Pay for customers who use them.

dense talon
#

Why it not showing to me even if in my mobile with gpay

hot dagger
dense talon
#

OKay

#

Okay so Apple Pay and Google Pay both are displayed from your end we did mistake for the his requirements

hot dagger
#

I see both on the URL shared in the related browsers, yes

dense talon
#

Can you please ss for the apple pay?

hot dagger
#

Nothing seems to load in Safari

dense talon
hot dagger
#

No Apple Pay. I suspect that's because the top-level domain (www.simpletix.com) isn't registered

dense talon
#

As above @fossil sage mentioned that, They have been able to see apple pay.

dense talon
#

Could you please confirm that both are showing correctly?

#

Apple/Google Pay

hot dagger
#

But that was a different URL. The URL you just sent me to is not registered for PMDs

dense talon
#

let me share proper URL with this domain

hot dagger
#

I know it is, but both the top-level domain (www.simpletix.com) and the iframe domain (embed.stg.simpletix.com) need to be registered:

If the top-level domain differs from the iframe domain, the top-level domain and the iframeโ€™s source domain must both be registered payment method domains on the associated account.
https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#using-an-iframe

Register domains to use payment methods (including Link, Apple Pay, and Google Pay) in Elements or Checkout's embeddable payment form.

hot dagger
#

www.simpletix.com is not

#

Please, just read what I'm telling you

dense talon
#

Ok

hot dagger
#

The direct embed URLs will work yes, because they're not embedded in an iframe. Once you embed them onto a different URL via an iframe then both URLs must be registered

dense talon
#

Okay got it so from above are you able to see both?

hot dagger
#

But not when it is embedded in an iframe as explained

dense talon
#

Okay mate got it

#

I need to registered both domains

hot dagger
#

You just need to add www.simpletix.com yes

dense talon
#

ok

#

And rest of the payment methods if we want then just we need to enabled first from the platform then only merchant have ability to enable from their end.

hot dagger
#

What other payment methods?

#

As Toby stated, they need to be enabled on your Connect config

dense talon
#

ok

#

got it

#

thanks, mate. I cleared all my doubts.