#dilkw-android
1 messages · Page 1 of 1 (latest)
that guide doesn't use the component in your screenshot though
that's the PaymentMethodsActivity, and the way it works is based on the Customer and EphemeralKey you create (it lists any PaymentMethods attached to the customer being used ) : https://stripe.com/docs/mobile/android/basic#set-up-ephemeral-key-server-side
My implementation process is that the server creates paymentIntent, the client obtains client_sercet, the client confrim, and then notifies the server capture
I only partially followed the guide
sounds good so far!
So, how should I achieve the effect in the picture
that's the PaymentMethodsActivity, and the way it works is based on the Customer and EphemeralKey you create (it lists any PaymentMethods attached to the customer being used ) : https://stripe.com/docs/mobile/android/basic#set-up-ephemeral-key-server-side
it's a different integration to just getting the card details from a single input and confirming the PaymentIntent directly
How should I attach paymentMethod to the user
if you want something like the screenshot you should use the "pre-built UI" guides, not the "card element only" ones really
the component does it for you when the user enters their card details
At which step will the user be associated with the card, and the card list can be displayed during the next payment
it's covered in the links I shared.