#AlexPanda - Stripe Elements

1 messages · Page 1 of 1 (latest)

runic plume
#

Hi 👋

#

Can you share the doc you are using?

smoky loom
runic plume
#

Okay and what Stripe Elements are you using?

#

Both Stripe Card and Payment Elements will defer rendering the Postal code based on specifics of country and payment method depending on what is required to validate the payment method.

smoky loom
#

Its the customizable version, where each element (card number, expiry and cvc) is mounted manually to create a custom looking form.

runic plume
#

So, to answer your question, we use the data when it is determined it is required. I do not know all the considerations that go into requiring the postal code info

smoky loom
#

but if I supply the postal/zip code in the owner.address object when creating the source, will this be used in fraud prevention by Stripe?

runic plume
#

If we determine it's necessary AFAIK.

smoky loom
#

alright, I was just worried that Stripe lost access to this field since I do not see it in the owner details, when viewing the payment/customer data in the test mode dashboard

#

especially when reviewing the event log and seeing address_zip_check=null

plain summit
#

👋 stepping in here as Snufkin needs to step away. Let me know if there is anything outstanding that I can help with here!

smoky loom
#

Thanks!, I'm just looking to confirm that the way I'm supplying the postal/zip code is sifficient for Stripe to do its anti-fraud magic with Radar, etc.

The address_zip_check=null point is the reason I am unsure its working

plain summit
#

Gotcha. And you are using Card Element?

smoky loom
#

using the custom form layout, where each element (card number, expiry and cvc) is mounted manually

plain summit
#

Gotcha. So in this case you would create your own form to collect postal code and then pass that to confirmCardPayment. With the split Elements flow there isn't a Postal Code Element.

smoky loom
plain summit
#

Oh okay that sounds fine. Though I don't really recommend using Sources as that is our legacy integration. Can you provide an example I can look at where you are seeing the zip as null?

smoky loom
#

I expected that after providing the zip, that the Stripe dashboard for the payment method would show the zip in the Billing details section, but it doesnt.

This made me check the event log, and the charge.succeeded event had the source object with the following card

"card": {
        "exp_month": 2,
        "exp_year": 2025,
        "last4": "4242",
        "country": "US",
        "brand": "Visa",
        "funding": "credit",
        "fingerprint": "eFxdoA4Ve2HJ8XsH",
        "three_d_secure": "optional",
        "name": null,
        "address_line1_check": null,
        "address_zip_check": null,
        "cvc_check": null,
        "tokenization_method": null,
        "dynamic_last4": null
      },
#

The address_zip_check make me think the zip is unused, but I have no way to know, so wanted to confirm

#

(and yes we are working on moving from source API to PaymentIntent, but its a large refactor so I need to use sources for now)

#

I can provide and event ID for the test mode data if that would help

plain summit
#

Yeah that would help.

smoky loom
#

evt_3LA2V1ATydeHsTlR2sNZl7tZ

mental meteor
#

Hello 👋
Taking over here
Give me a few to catch up, thanks 🙂

mental meteor
#

Appreciate your patience, still looking into it