#benk

1 messages · Page 1 of 1 (latest)

sudden ploverBOT
coarse aspen
#

What's the issue?

slender void
#

we are investigating the requirements for adding ApplePay to our own hosted payment page

#

but it turns out that's an older version and v2 has been since deprecated

#

To my understanding Elements and Checkout are mostly used for Strip hosted payment pages, whereas we host our own payment page

coarse aspen
slender void
#

but the Payment Request Button option still requires using Elements rght?

coarse aspen
#

Yes, the SDK/API uses Stripe.js

#

I don't know what you mean by 'requires using Elements'

slender void
coarse aspen
#

Yep, you're using Stripe.js and the Payment Request button is an 'Element' so to speak

slender void
#

ok got it

#

on more question

#

is it possible to load the ApplePay button and set it up other than through the Stripe.js?

coarse aspen
#

You can do a direct integration with the Apple Pay API/SDK, sure But that is far more involved and convoluted and we don't have any specific documentation on that

#

Why are you so adverse to using Stripe.js?

slender void
#

we have our own payment page and we would like to setup the ApplePay which is PSP agnostic, eg: not to hardcode Stripe as the only vendor for the ApplePay button but able to d some clever stuff working out which PSP we would like to set up and then based on that display the configured ApplePay button

coarse aspen
#

Sure, then you can integrate directly with Apple Pay. That will generate a Apple Pay token that can be used to create a Stripe token

slender void
#

we have a list of clients with different Payment Service Provider and would want to setup the ApplePay in a generic manner which would support multiple PSPs when displayed on our payment page

#

is there a Stripe specific docs for this on how to create the Stripe token from the ApplePay token?

coarse aspen
sudden ploverBOT