#korra-hostedinvoice-phonenumber
long plaza
Can you describe the part of your your integration your asking about? How are you taking payment using Stripe?
narrow valleyBOT
grand vale
At the moment we are using the stripe provided subscription purchase pages, you can add use of apple pay and google pay along with other payment methods through the dashboard
Challenge: Our downstream auth system depends on the presense of the phone number in the payload, if the user currently pays through gpay for example, the stripe default appears to be using the min set of fields which doesn't pass phone number.
drifting crater
Are you using Checkout? If so it has an option to force phone number collection https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-phone_number_collection
I don't think the hosted invoice page has an equivalent option unfortunately. I can put in a feature request but for now you would need to either use Checkout or collect the phone number on your own custom page before creating the subscription
narrow valleyBOT
worn sonnet
korra-hostedinvoice-phonenumber
grand vale
Thank you. I think we may be stuck with some back of house operational toil as long as we use their out-of-the-box invoice pages for subscription purchasing.
We already have phone number forced when a credit card is entered in the checkout, but if the user selects google or apple pay as the quick pay method, we are getting MIN address information which doesn't provide phone number.
worn sonnet
If you use Checkout it should "just work" though
grand vale
Source GooglePay Dev docs:https://developers.google.com/pay/api/web/reference/response-objects#Address
worn sonnet
We abstract Apple Pay and Google Pay for you
grand vale
That's the challange
It looks like in that abstraction you have: MIN address format may be returned if billingAddressFormat is set to MIN
For google pay at least
There is no config that I can find in the dashboard on the config of payment methods that allows us to up to full
worn sonnet
Do you have a concrete example Session where you required phone number and it didn't get provided?
worn sonnet
If you can give me a Checkout Session id cs_test_123 or cs_live_123 I can check
grand vale
Hold tight
Apologies, this may not be what you asked me for: cus_O2YdfYQoaFShcm.
This is a customer I just created through the subscription purchase page
worn sonnet
what do you call "the subscription purchase page"
worn sonnet
Okay, taking a step back because understanding your overall integration is crucial to be able to grasp Stripe and our features
grand vale
Sure.
Understanding our use case and current context of the issue relative what we are using stripe for will also help
worn sonnet
This is a URL for a Checkout Session. The id I needed is cs_live_a1reIOuw7NLWNob6ATGyHfxAYh1ok4AfhknB53FqgFwNV5aPOr4FIJGSRj which is inside that URL.
That URL doesn't come from you using Checkout directly though. It seems you are using a no-code product solution called PricingTable and the docs for it at https://stripe.com/docs/payments/checkout/pricing-table
That Session is not configured for phone number collection right now so it's expected there's no phone number
grand vale
And how can we change that?
All payment methods must collect and pass phone number on a newly created customer
worn sonnet
PricingTables are configured straight from the Dashboard and there's an option for this and you likely didn't enable this
grand vale
Sweet!
worn sonnet
so you need to change your PricingTable to support this
grand vale
Ok. I'm in the pricing tables we currently have configured
I see payment methods
Phone number collection is configured
Howwever if a user selects a google or apple payment method they appear to by pass the need to add a phone number
worn sonnet
Phone number collection is not enabled on your Checkout Session
I'm looking into why, give me a few minutes
grand vale
Thank you much!
worn sonnet
Can you create a brand new Session? Like click on the button to get to Checkout and give me a new URL/id just to make sure it isn't because you changed that option since
grand vale
Sure thing
The main concern is customers pay with google and apple pay not having phone numbers passed in. CC entry forces phone collection
grand vale
derp. Test sub issue.
Let me run a transaction via google pay on this and see if the customter payload comes in with phone, gim sec
I'm a burned out dork.
Yep. It passed in the phone number as expected
Thank you, lesson for me is to make sure that when we configure out pricing tables we ensure phone number collection is turned on and all our payment methods will pass us what we need. yes?
worn sonnet
yes!