#themax1-payments

1 messages · Page 1 of 1 (latest)

cerulean thicket
#

If you're using the Stripe React Native SDK, it's using the Payment Element to collect payment details. Checkout and Elements host all form inputs containing card data within an iframe served from Stripe’s domain—not yours—so your customers’ card information never touches your servers.

you can probably take a look at ths too : https://stripe.com/docs/security/guide#validating-pci-compliance

flat blaze
#

Hmm, so I have to use the payment elements? Because I was trying to create my own inputs and handle this with my backend

#

I saw there is a elements cards only to get the card, but in the tutorial it doesn't say how he's collect the card details

flat blaze
#

Did he get automatically the card details from the card form?

#

I click on card element only and there's a onCardDetails there's a console log

#

He get the value automatically?

#

This part:

<CardField postalCodeEnabled={true} placeholder={{ number: '4242 4242 4242 4242', }} cardStyle={{ backgroundColor: '#FFFFFF', textColor: '#000000', }} style={{ width: '100%', height: 50, marginVertical: 30, }} onCardChange={(cardDetails) => { console.log('cardDetails', cardDetails); }} onFocus={(focusedField) => { console.log('focusField', focusedField); }} />

#

It seems his not handling the onCardChange

#

Unless he ties the cardField values auto if the request then

#

That's what's confusing me

cerulean thicket
#

what guide are you referring to? can you share the link?

flat blaze
#

I think is auto then

#

Using CardField

#

He gets the information auto and send to a payment intent

#

So in the end it's better to use the SDk over the backend right?

#

Going to try out this SDk version tomorrow

#

I think using this CardField he ties auto with the request the way is in the tutorial

#

I was not going to store the card on my DB, only create the payment method that stripes provide on the API side, but maybe is not that safe I think

#

That's is the confusing part for me

cerulean thicket
#

If you collect the raw credit card numbers in your custom form and then use the Stripe API directly to tokenize the cards. We actively discourage you from doing this because by handling raw card numbers directly you become subject to the full PCI compliance standards. In your case this means you’d have to submit a SAQ D form annually to prove that you are PCI compliant. It’s a 40 page form and trust me, not a headache you want to be dealing with.

flat blaze
#

Ohh gotcha

#

But you think using the method the SDk provides for UI is the best?

cerulean thicket
#

follow the guide, that's our recommended approach

flat blaze
#

Hmm gotcha

#

Going to try out tomorrow, going to bed now, can you leave this thread activated and tomorrow I confirm or if I have any questions I can ask here?

cerulean thicket
#

i'd suggest asking again in the main channel

#

the thread will automatically be archived by tomorrow, but you can always refer us back to this thread if there's something about what you said before that you want to discuss further, and we can reopen it if necessary

flat blaze
#

Ohh gotcha, that's fine then, ty for the help