#softnet_code
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1269941481964179541
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐ happy to help
Hi
both Apple and Google Pay are considered as card
for the renewal payments I can get the charge.PaymentMethod and generate new payment intent right?
please read through these docs https://docs.stripe.com/apple-pay and https://docs.stripe.com/google-pay
yes
check this https://docs.stripe.com/apple-pay/best-practices#best-practice-for-apple-pay-recurring-transaction for Apple Pay recurring transactions as well
is this applicable only for apple pay or also for google pay
just Apple Pay
got it
one more thing, we are not using setup intent but create payment intent. In our docuymentation I saw that this token authorisation works only with Setup intent
is there any other work around for this ?
you can use it with PaymentIntents when adding the setup_future_usage param in the PaymentIntent creation requestion
still its not clear
you want to pass some kind of token for apple pay when we create first time payment?
currently we are passing SetupFutureUsage = "off_session" for all other payment methods. is that enough for apple pay or we have to do something different?
no that is enough
Currently we are passing offsession=true and setupfutureusage=offsession for other payment method types
can we add apple payto our existing integration without changing the code as we have already have this setup
plz correct me if im wrong
yes
Improve authorization for your API integration
To implement recurring Apple Pay transactions using the API:
Save the DPAN (or MPAN) and cryptogram in a Card.
Initiate a CIT to consume the cryptogram before its expiration. Send a 0 USD validation or a charge transaction to the authorization network, and keep a record of the returned network transaction.
Reuse the payment method for future off-session MITs. Stripe sends the DPAN (or MPAN) and the network transaction ID of the original CIT to the authorization network to improve authorization rate.
Consume cryptograms as soon as they are created using the following recommendations.
I saw some section in the link you have shared
do we need to do something in our code to acheive this?
this is not mentiond in the document
this is an extra step, an optimization if you want
but it would still work without it
Add Apple Pay merchant tokens
You can add a merchant token when presenting Apple Pay in the Express Checkout Element, web Payment Element, and mobile Payment Element. Stripe automatically handles merchant token requests in Stripe Checkout integrations.
Express Checkout Element
Web Payment Element
Create an instance of the Payment Element.
Pass the applePay object relevant to your MPAN use case (choose from the drop-down to see use case code samples).
Include relevant parameters for your use case.
we also found this section
currently we are using stripe element on the UI
we have card, ideal payments, now we are going to add apple pay and google pay
to support recurreing payments do we need to modify anything on the UI? We have added google pay and apple pay in the stripe dashboard and we manage to create payment using apple pay/google pay without modifiying anything on the UI. Hope this works fine for the renwals also
no you don't have to change your current implementation
you just need to register your domain as explained in the docs that I sent you and enable the PaymentMethods in your dashboard
and you should be good to go
we did already and we manage to complete the payment
but the part which is not clear to me is that, they mention in the document for the renewals, we need to do something different like capturing MPAN
again, this is not necessary
this is an optimization
like if you see that you're getting a lot of declines in recurring payments we could look at this then
but for now you should be good to go
Thanks for your time. I will reach out to you if we face any further issues.