#nicolaujr-elements

1 messages · Page 1 of 1 (latest)

noble trout
#

hi there, no, this isn't all possible using elements. I guess the question here is what "relevant" data are you looking for specifically? Because SSN shouldn't be required for a customer to make payment

granite rover
#

Hi, I'm from Brazil, and here, SSN is the CPF

#

What I'm actually trying to do, is prevent disputes

#

and make sure that I have all the relevant data, to prevent disputes with credit card

#

I had problems with that once

#

I provide a service, selling digital content

#

so, there is no product, sending receits or anything of the sorte

#

sort*

#

Just the customer accessing the content

#

And I want to make sure that I'm doing everything right

noble trout
granite rover
#

Ok, Thank you @noble trout

#

I will look at the disputes link 👍

#

The contact link is how I found the discord channel 😅

noble trout
#

i find the contact form can be pretty confusing to use, are you having trouble figuring out how to contact Stripe Support? You need to click on Contact support on the upper right hand side

granite rover
#

That is true, is kind of confusing, I believe because is different from the mainstream

#

the chat and contact is usually in the bottom

#

But thanks

#

👍 😃

noble trout
#

you're welcome!

granite rover
#

Another question

#

On the disputes docs

#

It's say on "Colete o maior número possível de dados de pagamento"

#

sorry, it's in portugues

#

but, it's say to collect the most of the data payments

#

and says to use the Elements

#

to collect customer name, email, postal code, and delivery address

#

How can I make the elements requests this fields

#

using the elements, only asks for the credit card data end the country

noble trout
#

are you referring to this section?

granite rover
#

Yes

#

Do I need to send the customer data from the server side?

#

I'm using the PaymentIntent API

#

with Python

#
intent = stripe.PaymentIntent.create(
            amount=data['payload']['amount'],
            currency=data['payload']['currency'],
            automatic_payment_methods=data['payload']['automatic_payment_methods'],
            metadata=data['payload']['metadata']
        )
#

pretty much that is the code

noble trout
#

to clarify, Elements allow you to customize your own Checkout form. What this means is that you would probably need to define those fields e.g. name, email, address, etc in your own form in order to ensure that you're always collecting these details.

By default, the Payment Element will collect all necessary details to complete a payment.

For some payment methods, this means that the Payment Element will collect details like name or email that you may have already collected from the user. If this is the case, you can prevent the Payment Element from collecting these data by using the fields option.

#

If you want something easier to setup, you can look into using Stripe Checkout instead

granite rover
#

can you send me the documentation where it describes that behavior

#

?

#

I've tried to find, but without any luck

noble trout
granite rover
#

I mean the Elements behaviour

#

to customize the fields

noble trout
granite rover
#

I see

#

maybe I will git the checkou a go

#

But thanks again @noble trout 👍