devAgam

[winged lodge]

Yes, generally speaking, but with the caveat that you need to adhere to guidance for the individual wallets

[grim drum]

Could you please link me to appropriate docs, im having a hard time finding those

[winged lodge]

https://stripe.com/docs/apple-pay?platform=web#recurring-payments

Apple's docs about this are a bit hard to find

one moment

[grim drum]

Yea i found that doc on stripe but it doesn't seem to point to what to do programmatically unlike the card element guide

not even sure what is an Apple Pay token

I've implemented the recurring payments on the card element not sure how much of that code can be copied over for buttons

[winged lodge]

I mean details like this: https://developer.apple.com/app-store/review/guidelines/#subscriptions
https://developer.apple.com/design/human-interface-guidelines/technologies/apple-pay/subscriptions-and-donations

They seem to have reorganized their docs so I'm not sure if/where the various recurring payment models are listed

[grim drum]

Righttt

for now could you point me to docs that are specific to google pay

since im in India i will only be able to test with that

and usually google docs are a lot more forgiving compared to Appl

[winged lodge]

Currently Google Pay and Apple Pay are not supported for customers in India: https://support.stripe.com/questions/supported-payment-methods-currencies-and-businesses-for-stripe-accounts-in-india

[grim drum]

Well that is rather unexpected

well could you still point me to the docs i'll just have someone in the states test it for me

since the application is set to be used in the US

[winged lodge]

I'm not aware of any specific docs for google pay recurring payments

[grim drum]

well any doc that has the details of the functions and api which need be used for creating a sub on the wallets

cause i cannot find any one which specifies what functions to call

[winged lodge]

In general the way this works is using the payment method you get back from the PRB and either attaching it to a customer or confirming a setup intent instead of a payment intent if you have no up-front payment (and using setup future usage if you do have a payment up front)

[grim drum]

PRB ?

[winged lodge]

Payment Request Button

[grim drum]

ah

So whereas we create a customer, a subscriptions and then collect payment info in Card Element

we have to create a payment method and pass it to the PRB ?

wait no

[winged lodge]

No the payment request button produces the payment method

[grim drum]

righttt

[winged lodge]

If you are creating the subscription following our doc, you should be able to use the payment method you get to confirm the first invoice payment intent

[grim drum]

yea im able to get the payment intent for the card element

im just not sure where to pass it here

for cards its confirmCardPayment(clientSecret)

not sure how it translates for button elements

[winged lodge]

its still a card 🙂

google pay / apple pay payment methods are just representations of the underlying card

[grim drum]

right

[winged lodge]

https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-complete-payment

The doc here shows the confirm snippet using the PRB-produced PM

[grim drum]

ahhhhh

[winged lodge]

paymentRequest.on('paymentmethod', async (ev) => {
  // Confirm the PaymentIntent without handling potential next actions (yet).
  const {paymentIntent, error: confirmError} = await stripe.confirmCardPayment(
    clientSecret,
    {payment_method: ev.paymentMethod.id},
    {handleActions: false}
  );
...

[grim drum]

got it

got it got it

thanks!

[winged lodge]

NP!