36korrawit40

[subtle rain]

I'm not sure, are you not able to set your own wallet information to that? I dont think we have any specific guidance for this.

[shell venture]

There is a preexisting thread on this. Stripe doesn't guarantee E.160 fomat from Apple Pay. In Stripes pipeline, you drop the ISO country code and do not transform the phone string to include +country code.

This forces us to make assumptions and correct numbers that appear in the customer object that arrive with no <+ country code>

I need to mimic a customer payload that has a string of digits in phone that lack + counrty code

So either i test in production and risk downstream customer impact since access to services is granted by phone number, or I find a way to manufacture a customer object that is assocated with a subscription where the phone data fits the pattern we see from customers created when they make an apple pay transaction. 🙂

Clear as mud right?

-- Looks like Stripe Postman may let me do this

[subtle rain]

Oh, good. If you want to share what you're doing if that works for you, that would be helpful.

[shell venture]

what's the best way to do that?

[subtle rain]

I mean sharing here, any docs you followed or values you used

[shell venture]

I don't use discord often so I dont know how to kick off a call or whatever

Got it. Let me test a path here with postman and see if it works.