#emiljonssom12344321

1 messages · Page 1 of 1 (latest)

dry needleBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

past pewter
#

Are you using direct charge or destination charge?

thin shell
#

direct charge i guess, what are the difference?

past pewter
#

Direct charges are created in the connected accounts, so you need to register their domains on behalf of them for Apple Pay

#

Destination charges are created in platform, so you just need to register their domains on your account for Apple Pay.

thin shell
#

so basically we are not using stripe connect, each client has its own integration to our platform and their own domain

past pewter
#

Then they need to register the Apple pay domain by themselve

thin shell
past pewter
thin shell
#

our solution is a script and a div, so stripe isnt really implemented on our clients webpages

#

it is via a script and a div.

#

you can see it for yourself bu going to the above domain and click the book button

dreamy nova
#

Hi! I'm taking over this thread.

#

if the hosted Checkout Session is hosted on example.com, then the merchant needs to register the domain example.com

thin shell
#

ok so not the domain of the plugin?

dreamy nova
#

I don't understand what that means.

thin shell
#

we are a saas company providing a bookingsystem, the bookingsystem is implemented on our clients websites using this script: <script src="https://plugin.rentalbuddy.io/static/js/main.js"></script>

here is an example where the script is implemented: https://gokaya.se/site/gokaya-demo-site-unmanned/

what of the domains needs verification?

#

the domain in the plugin or the one where the plugin is implemented on