#david-checkout-shipping

1 messages ยท Page 1 of 1 (latest)

shy meteorBOT
hallow violet
#

Hello ๐Ÿ‘‹
Can you share an example event ID?

#

evt_xxx where you're seeing the above information as null

supple thunder
#

cs_test_a1EafqEHX1exXuE1LtIrmlEfGMe01henzVKJ4ifJhZe3mEE6Rtk9dVh4DB looks like one.

hallow violet
#

that works too, looking..

supple thunder
#

And that doesn't get associated with the customer when using always? What's the proper place to put that information?

hallow violet
#

afaik, no. It's only associated with that particular Session/PaymentIntent

#

I could be wrong though, looking

supple thunder
#

For the purposes of developing this fulfillment function, where should I be editing the default, stripe-supplied, fixtures to get a valid customer email address?

hallow violet
supple thunder
#

That seems a bit odd. The response back in the checkout session object sent to my function includes a customer clause, but with all the fields set to null.

#

Unlike the line_items object, which you do have to request specifically and is not present at all in the object by default.

hallow violet
#

I think the response would only have customer ID (since it's an expandable field)

supple thunder
#

But the customer field (where the ID is stored in the checkout session object, IIRC), is also null. ๐Ÿ˜ฆ

hallow violet
supple thunder
hallow violet
#

"customer": "cus_OfVTE9zehxWWHa",

supple thunder
#

!!

#

Geez. I've been running through so many versions that I didn't even see that....

#

So returning a customer ID and customer_details set to null is expected behavior?

hallow violet
#

I think it might be, double checking with a colleague

supple thunder
#

Thanks. ๐Ÿ™‚

hallow violet
supple thunder
#

Checking...

shy meteorBOT
waxen bay
#

david-checkout-shipping

supple thunder
#

Yup. That seems to do it.

#

A little odd that you have to specifically request that after getting back a null object, but I'll go with it. ๐Ÿ™‚

#

Thanks for the help! My ultimate is ready. ๐Ÿ‰