People Against Passwords

:birthday_party_parrot::beetle::facepunch: Stripe Phone Number Data Quality --&gt; Overcoming their laziness.

<https://stripe.com/docs/payments/checkout/phone-numbers#after-session|Stripe admits unwillingness to ensure phone data quality from apple pay>

Any Subscription business using Stripe and OTP for product access should expect bad phone data coming from Apple pay payments.

How we solved for it &gt;&gt;&gt; Go Deeper in the sub thread.

1. *Quick &amp; Temporary:* We’re using a simple approach for phone numbers, assuming US format (+1 &amp; 10 digits) due to our focus on US, CA, LA based customers. Also, we’ve added a custom attribute in Descope for Stripe customer_id and logic for PII updates. It’s not perfect but works for now, and we’ve documented it for future refinement.
2. *Better (but more work):* Later, we’ll fetch ISO country codes by expanding the Payment Method object to access `billing_details.address.country` in Stripe. See <https://stripe.com/docs/api/payment_methods/object|docs>.
3. *Long-term Solution:* We aim for a lightweight customer management system with entity resolution, which will enable us to create a reliable, unified customer profile using data from all our systems, plus additional insights and automation.