#shaya8089

1 messages ยท Page 1 of 1 (latest)

winged raftBOT
copper shoal
winged raftBOT
winged plume
#

Hi @copper shoal thanks for your reply!

No, it's not working in live
And it makes me wonder since when I implement Apple Pay directly I do manage to open the payment dialog and I don't get this error.
I guess that the reason is that as I mentioned about:blank is matching the top level origin domain.

But to the second part of my question:

Is it possible to make it work using Apple Pay's API directly (and not using Stripe's Payment Request Button)?

Thanks again for the help

#

This is a screenshot of our iframe as it's rendered on the client's website
(Note that it has the allow="payment" attribute)

clear talon
#

Hi ๐Ÿ‘‹

I'm stepping in has @copper shoal needs to go soon

#

Is it possible to make it work using Apple Pay's API directly (and not using Stripe's Payment Request Button)?
What exactly are you trying to do here?

winged plume
#

I want to enable Apple Pay for our end users
As I described I'm getting the following error in Safari

clear talon
#

If you are are tying to generate a Stripe payment method from your own Apple Pay integration you can use the Apple Pay token to create a Stripe payment method. As long as your domain is registered with Stripe

winged plume
#

Which domain needs to be registered with Stripe? every single domain that embeds our product to their website (after connecting their Stripe account to ours)?

clear talon
#

The top level domain that the charges are created for

winged plume
#

When we create a charge for our customer on their website using Connect - what is considered the top level domain for that? the customers website?

clear talon
#

What type of Connected accounts are they?

winged plume
#

Standard account