#Steve1662

1 messages · Page 1 of 1 (latest)

storm orchidBOT
runic mango
#

Can you share the details about how you initialize stripe.js and share an example payment?

#

Are you using direct charges for this?

lofty cedar
#

Sure. Here is the client side init...

#

What would you like for an example payment?

#

Payment intent id or something?

#

Not sure what direct charges means. We use payment intents and set an application fee to take our cut. In call calls to the Stripe API we pass a our Stripe account info along with the connected account number.

runic mango
#

Which is what you're doing

lofty cedar
#

Good to know.

runic mango
#

So with standard accounts and direct charges, yes the domain needs to be registered with apple pay, but the button shouldn't appear unless that's in place already

#

Note that as a platform you need to perform this registration using your platform keys and the same stripe-account header for use with direct charges:

lofty cedar
#

Understood on doing the domain registration.

runic mango
lofty cedar
#

Given that it should not show that means the behavior is then unexpected.

runic mango
#

And this is where an example payment would be helpful, so i can see what is in place for a given account where you're seeing issues

lofty cedar
#

acct_1BHtPIEEh9cdAk0g
pi_3MFHNTEEh9cdAk0g1Y5ASGa4

#

You can see the checkout experience at https://trytn.dev. Click the book now button, add something to your cart and punch thru to the review step.

#

Not that as of now I have deleted the Apple Pay domain associated with that account. When I add the domain the Apple Pay experience works as expected.

runic mango
#

Yep, that's all expected

#

Note that you need to use your live platform SK to set this up

lofty cedar
#

Correct. We did not start out always using the live key but have caught and fixed that.

#

So is the display of the Apple Pay button when the connected account does not have a verified Apple Pay domain a bug or are we missing some configuration?

runic mango
#

For that account it looks like you only set up the domain using your test keys, which is the config problem here

lofty cedar
#

Ok... so I will attempt to use the test key to pull the domains via the API and then delete them thru the API.

runic mango
#

and then make sure to configure them using the live key, yea

lofty cedar
#

I've deleted those domains. When I list the domains with either the test key or production key I see no domains. Testing thru trytn.dev I see the Apple Pay option. pi_3MFHNTEEh9cdAk0g1Y5ASGa4

runic mango
#

Yea, so, that bit is an artifact of the underlying system

#

If you re-do the registration using connect+stripe-account header using your live key, you should be able to complete that

lofty cedar
#

Understood that is what I need to do to make it work for that account. But the problem that I have is that I would not expect the Apple Pay button to display for any tenant within our system that has not setup their Apple Pay domain via our system. The account we've been using is now in that category.... aka no Apple Pay domain setup. The question I have is should that Apple Pay option be showing if they do not have a registered domain.

runic mango
#

Well it was previously set up, so its not exactly a good test case for having never been set up

lofty cedar
#

Seems that when we call the delete domain call that some residue is left behind. Also we had going live with our implementation and rolled it back because accounts that had never had a domain registration did show the Apple Pay option. This was before we were registering domains via the API but rather doing it via the connected accounts dashboard.

#

I will update the account behind trytn.dev to use a different stripe account that has not had domains added (via dashboard or API). Hopefully this will just work else it will be a good example to see the issue.