#Gyan
steep smelt
I'd suggest using the combined payment element for mobile flows to support all your payment methods at once
Yes, the above document mobile payment element is our recommended pattern
https://stripe.com/docs/payments/accept-a-payment?platform=react-native&ui=payment-sheet#react-native-collect-payment-details
onyx fulcrumBOT
sour wyvern
will it support both ACH and card payments?
steep smelt
Yep!
iron wind
Hi taking over for synthrider as they have to step out
Not quite: A Customer Ephemeral Key (optional). Information on the Customer object is sensitive, and can’t be retrieved directly from an app. An Ephemeral Key grants the SDK temporary access to the Customer.
sour wyvern
i already have a "create payment intent" and "create customer" API, do we still need ephemeral key to accept payments through the combined payment Element UI?
iron wind
You probably want to use the ephemeral key if you want to save the card to the customer:
Note
If you never save cards to a Customer and don’t allow returning Customers to reuse saved cards, you can omit the Customer and Customer Ephemeral Key objects from your integration.```oh nice.. yes we are not saving card details for returning customer for now. So we can skip that, correct?
iron wind
Yeah
sour wyvern
Thanks, one more question on ACH payment, how pulling up existing verified bank accounts for the customers are done with this UI?
And will i be required to take agreement on the T&C message saying "thank you for signing up for direct debits" shown to the customer which was required in web integration?
onyx fulcrumBOT
amber estuary
👋 stepping in for my teammate! Give me a sec to catch up
You will need to present a customer with terms. More details on that are available here: https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=mobile&ui=ios#ios-collect-mandate-and-submit
