xiao-postal-code | Stripe Developers | Page 1

quick stream Nov 3, 2021, 5:24 PM

#

@silent mirage asking first but since you have a support engineer helping you on this, why not ask them directly instead of coming and doing this in public?

silent mirage Nov 3, 2021, 5:25 PM

#

@quick stream thx! She is not sure about the answer and directed me to this channel to confirm

quick stream Nov 3, 2021, 5:25 PM

#

can you DM me the name of your contact? They really should not be sending you to Discord for help

#

To answer your question though billing_details is in the response. It's after the charge is created. It has a "record" of what was sent to the card network (or any banking partner)

#

The place where you pass the postal code is when you collect payment method details client-side. It's not on the PaymentIntent or the Charge itself

silent mirage Nov 3, 2021, 5:29 PM

#

@quick stream thanks! Good to know! This is what we are doing now: collect zipcode during creating payment method stage for US cards in order to save the Visa integrity fee. Got confused because our support eng suggested as above that even we collect a card's zipcode, but passing the zipcode as param for each future charge request on that card we vaulted can help improve the approval rate

quick stream Nov 3, 2021, 5:31 PM

#

yeah they are not correct, they must be confused

#

you can confirm by reading the resulting Charge (the ch_123) which exists in both cases and look at billing_details

silent mirage Nov 3, 2021, 5:32 PM

#

Yes, our team has found that there is typically a benefit from passing zip on every charge so we would recommend testing this. If you start this let me know.

#

this is the reply I got before

quick stream Nov 3, 2021, 5:32 PM

#

yeah they are likely confused/unclear. But hopefully now you're unblocked

#

please DM me the person's name/email just for me to follow up internally!

silent mirage Nov 3, 2021, 5:33 PM

#

The question I asked before

Would you like to give us some updates in regards to question #6? Have you checked with your team that passing zip for every US charge could increase payment success rate based on the data you have, even Stripe already stored the zipcode for us when creating payment method? We are happy to start a AB testing for this.

quick stream Nov 3, 2021, 5:37 PM

#

yeah I'd recommend following up with them directly

#

But overall are you unblocked as to how to confirm the postal code is collected/passed?

silent mirage Nov 3, 2021, 5:38 PM

#

Thanks @quick stream! Let me follow up with them!

quick stream Nov 3, 2021, 5:38 PM

#

If you have a concrete example pi_123 or ch_123 I can confirm too

silent mirage Nov 3, 2021, 5:42 PM

#

@quick stream yes, you are correct. I found that zipcode is already in the response if we have it stored before.

For example ch_3JrnR1HNlon6vqsn1KMb7n2M

quick stream Nov 3, 2021, 5:45 PM

#

yeah so chatting internally it seems they explained exactly the issue, that some transactions don't have the postal code. For example the ones where you use Apple Pay. Have you investigated that?

silent mirage Nov 3, 2021, 5:48 PM

#

We only collect zipcode if the user is in US for cards and Apple Pay.

#

The idea is to save Visa integrity fee which only applies to US cards but also do not want to create extra frictions for non-US card holders by asking them to provide zip info

quick stream Nov 3, 2021, 6:00 PM

#

yeah but that seemed to be the discrepancy when I spoke to your contact. At this point it does look like you know how to pass/collect postal code and you need to align with your contact on next steps

#xiao-postal-code