#runjan

1 messages · Page 1 of 1 (latest)

glacial hemlockBOT
toxic crescent
#

hi! there aren't really any backend changes involved in supporting Google/Apple Pay in general.

#

there isn't really enough information here, since I don't know what source is or where you get that or what your frontend integration looks like(since it's the frontend that accepts card details and would implement Google/Apple Pay).

wraith merlin
#

but in my product customer take subscription and do one time payment and for this we use payment intents but now we want to implement google and apple pay in our product. so what changes are required from backend ?

toxic crescent
#

like I said, generally no changes happen on the backend

#

it's the frontend where things might change

wraith merlin
#

what changes on frontend can you tell me in deep because in stripe docs i does not found any proper detail regarding this

toxic crescent
#

I can't answer that without information on what your current frontend looks like or how it integrates.

wraith merlin
#

what information you want ?

toxic crescent
#

for example, the code of your frontend payment form.

#

or the guide you used when you built the integration

wraith merlin
#

in frontend we create a token and send to backend
in backend we create payment intent and send client secret to frontend
then frontend check payment confirm or not with paymentintent confirm api with client secret key ...
this is the process we are using now we want to the give options to customer to click on google and apple pay for payment.

toxic crescent
wraith merlin
#

i cannot understand anything

toxic crescent
#

sorry to hear that! what specific points can I clarify?

wraith merlin
#

can you tell me the whole process to integrate the google and apple pay form both client and server side requirement. suppose you want to add this feature to your product then whhat you do tell me this things.

toxic crescent