#Mr Stinky Pants
quasi gorge
worthy rover
Are you using the payment element?
Also are you specifically trying to collect shipping info?
ivory plank
yes payment element
i just thought it looks better in the dash board if you can see billing address straight away
without going in to payment method
worthy rover
Gotcha. You could use the api to set it on the customer: https://stripe.com/docs/api/customers/update#update_customer-address. So once the payment was successful, you could just update the customer's address via a webhook event
Just so you only have to collect address once
ivory plank
yes ive got all that just checking this is normal
i mean is it a matter of going to the customer and getting the default payment method id and calling paymentMethodService
worthy rover
Yeah it is normal
Alternatively you could use the address element: https://stripe.com/docs/elements/address-element/collect-addresses
And then update both the payment intent and customer object with the address value
ivory plank
yes im using that
worthy rover
Oh you said payment element
worthy rover
Yeah I know so I assumed you just used the payment element to collect address since you didn't mention also using the address element
Anyway, you could switch to a multipage checkout view to achieve what you want
In a multi-page checkout flow, you can manually update the PaymentIntent or update the Customer object with the address details received from the change event or getValue method before moving to the next step.```with subscription you need to make a customer first right?
i was doing 2 page but getting customer name etc first
worthy rover
Oh so if you already have multipage, then you can just manually update the customer with the collected address (and then also set the address on the PI if you so desire)
ivory plank
so customer should have the payment method can you expand that for the address?
or do you have to use PaymentMethodService
worthy rover
Not sure what you mean
You'd have to manually make the api call to update the customer's address
In a multi-page checkout flow, you can manually update the PaymentIntent or update the Customer object with the address details received from the change event or getValue method before moving to the next step.
Using the change event or getvalue
ivory plank
sorry codes getting pretty confusing
the only info you get at the start is this? setupIntent.PaymentMethodId
you have to to use PaymentMethodService on that id
worthy rover
The address element doesn't require a setupintent?
Are you sure you're using the address element?
worthy rover
Yeah and as I said you'd need to separate them into a multi-page flow
The next step is the payment element in ^
ivory plank
thats working cheers
when using a free trial how do you stop people keep signing up?
worthy rover
You'd need to keep track of signups, etc on your end (in your db)
So tie them to an email for example
ivory plank
but people can easily get more emails especially in a company
isnt there something relating to the card?
what is this fingerprint?
amber socket
Hi there 👋 taking over, as my colleague needs to step away
Yep. You can use the fingerprint to discern if someone has signed up multiple times with the same card. This is true.
ivory plank
so is that like a hash of the card number?
amber socket
It's a string that is consistent across multiple Payment Method objects
ivory plank
But what if a new customer on stripe with same card?
amber socket
Not sure what you mean
ivory plank
I mean a different customer with different customer Id signs up later with the same card
Will it have the same finger print?
amber socket
Yup. That's what it's there for: https://stripe.com/docs/api/cards/object#card_object-fingerprint