#papiwablo

1 messages · Page 1 of 1 (latest)

glass linden
raw bay
#

you have are called Card Elements

#

im looking to find out what type of Card Elements are available and how customizable they are

#

ty ty in advance

glass linden
raw bay
#

i think there is confusion on your part or the way i asked the question

#

there are prebuilt UI components provided by you

#

for instance you have a

STPPaymentCardTextField()

type

#

I am looking for a list of all the available types and the properties I can customize 😉

#

you seem to have 6 types

#

payment
wallet
address
card
link auth
cart ( says in beta )

crimson herald
#

👋 Hopping in here - so you're specifically talking about the mobile elements right?

raw bay
#

yes as evidenced by my inquiry as it relates to ios / swift / uikit 😉

crimson herald
#

Yeah the initial question was confusing because usually we refer to Elements when talking about our javascript library

#

The list you have of the 6 types is only for the javascript library - our ios library has a different sent of elements

raw bay
#

oh interesting. docs are a little quirky in their presentation.

#

yes the ios swift mobile native elements

#

where are the types available?

#

please and thank you

crimson herald
raw bay
#

ok -- i have another question but its not sufficient for this thread. should i ask in the main dev-help chat?

crimson herald
#

You can just conitnue asking here

raw bay
#

for iOS, i want to save a payment method without it being during a payment process.

#

in this client for example, a part of the sign up process is to enter a credit card, that will be saved for future use, but not processed immediately

#

i can already get the prereq setup intent information from our back end

#

i just need to find the method the simply pass the captured information to save only

#

please and thank you

#

everything i seem to come across is about doing it during a payment process, rather than just saving by itself

crimson herald
#

"i can already get the prereq setup intent information from our back end" -> Can you clarify what you mean by this?

raw bay
#

in order to save a payment Stripe, as i understnad it stripe requires you hit your back end for a setup intent and have clientSecret, CustomerrEphemeralKeySecret, publishableKeyResponse, customerID -- available to pass to Stripe

#

i just need to locate the method to SavePayment without presenting a built in UI

crimson herald
#

So are you having trouble using the Setup Intent to save a payment method, or do you already have Setup Intents working and you're not sure how to use the saved payment method in future payments?

raw bay
#

yes -- setup intent is no issue.

#

i just need the method on the ios side to pass info directly to stripe to save the payment method

#

the only example i can find require presenting a PaymentSheet, which i dont want to use prebuilt PaymentSheet in this case

crimson herald
#

What do you mean by saving the Payment Method? Using the Setup Intent is already saving the payment method - are you maybe asking how to attach it to a Customer?

raw bay
#

this is it

#

collecting the payment details

#

and submitting them to Stripe

#

your example shows only the usage of a prebuilt UI

#

i can successfully execute this -- what i cannot find is an example to do the same thing without your built in paymentsheet

crimson herald
#

Ah!So you're trying to do this with something like the card-only input?

raw bay
#

the example in the link above is exactly what i want to do with the exception of i do not want to use your built paymentsheet

#

therefore i need to know the methods you would use if i was using your Mobile Native Elements to collect information

crimson herald
raw bay
#

oOOOOOooOOOOoo

#

thiiiiis looks to be promising!

#

yes yes yes

#

i think this might be it

crimson herald
#

👍 awesome!

raw bay
#

yes this feels like the correct direction!

#

so there is one syntactical issue

#

in the documented example it says

// Collect card details
        let paymentMethodParams = cardTextField.paymentMethodParams
#

however XCode reports

Value of type 'STPPaymentCardTextField' has no member 'paymentMethodParams'
#

im using SPM 21.13.0

crimson herald
#

Hmm... that's strange - let me do some digging

raw bay
#

there is a .cardParams but it says its the wrong type

#

this problem also exists on the paymentIntent side as well

crimson herald
#

Ah - I believe the issue is the version you're using. Our public docs are written with the latest version of our libraries in mind, and paymentMethodParams was recently added in 23.0.0.

raw bay
#

yes im checking that now

#

I need

import StripePaymentsUI
#

which i dont believe is avail in 21.13.0

crimson herald
#

Yeah, that's something new for 23.0.0