#papiwablo - AWS Cognito
plush totem
The doc you referenced is making use of the clientSecret returned by the Setup Intent creation to initialize the Payment Element. Is this not working for you?
uneven solar
correct so let me explain here
bare with me please 😉
user signs up via AWS Cognito
our backend then kicks off account creation and setup intent process and returns me a clientsecret per your API documentation
front end captures card info and then return me a payment method token
i then send that token to my backend to be used / charged later
the backend documentation describes the object for setup intent here
this documentation makes no reference to customerEphemeralKeySecret
however in the first link i showed you
https://stripe.com/docs/payments/save-and-reuse
there is clearly a return of the customerEphemeralKeySecret that needs to happen from the backend and then be passed to Stripe
(thank you in advance)
in conclusion, my backend dev would appear to not be giving me everything I need because it would appear the API docs are inconclusive by not making mention of the customerEphemeralKeySecret -- whereas the example provided for the front requires customerEphemeralKeySecret
(again thank you)
plush totem
The page you referenced has multiple different workflows. Could you clarify which tab you are on?
plush totem
The last page you referenced where you state you need an ephemeral key. There are 5 tabs
uneven solar
The save and reuse example shows the backend returning a customer ephemeral key
The goal here is to get snag a payment method token and then store it in our backend
Will the “save and reuse” example return me a payment method token?
plush totem
Which version of the save and reuse doc? There are 5.
Prebuilt Checkout, Custom payment flow, iOS, Android, or React Native?
uneven solar
ios
My apologies on that
Thought it saved the segmented control position on the link I sent to you
plush totem
So in this case you are correct, you need both a client secret value and an ephemeral key
(as well as customer_ID and publishable_key)
And no, the URLs do not preserve which tab you send them to unless you copy the link from the right hand nav bar with the steps indicated on it.
In this case, everything you need from your server is on Step 2: https://stripe.com/docs/payments/save-and-reuse?platform=ios&ui=payment-sheet#ios-add-server-endpoint
uneven solar
Yep!
One last question then
My backend dev has been looking at this for the setupintent
From their perspective there was no mention of an empheral key
What’s the best documentation for them so they and I are best sync’d?
Is the above link not comprehensive enough, or not recommended best practice? Was this particular bit of information missing?
plush totem
I would reference the link I provided above and make sure you are clear that it's the iOS payment flow you are looking for.
I got the link I sent by selecting the step "Add an endpoint" from the "On this Page" menu while I had the iOS tab selected. It ensures the platform is encoded in the URL.
uneven solar
Thank you for the confirmation
plush totem
👍