#notdpr-checkout-email

1 messages · Page 1 of 1 (latest)

amber jettyBOT
lunar sorrel
#

notdpr-checkout-email

#

Let's take this one step at a time

The customer, if present. In the example below, there is a customer, but the customer.email is null.
what does that mean?

spark estuary
#

There's a customer field in the charge.succeeded event data, with a value cus_MtkC0gIkAWu7tb. When we retreive that customer, the email field is null

lunar sorrel
#

you created that email yourself, not Checkout (or your user did)

#

that's why it's null

spark estuary
#

ok... you mean like the account owner went into the Stripe dashboard and created an invoice and charged it?

#

"created email", did you mean "created customer" ? (sorry, I'm confused 🙂

lunar sorrel
#

The Customer id you gave me is a Customer that was created before any Invoice or Checkout Session or anything. Not even with the Dashboard. Since that customer was created via the API with no email, it's expected that there's no email

#

it's basically the same thing we discussed the other day I think: because your users can do whatever they want with their account, you end up having to rely on many fallbacks 😅

spark estuary
#

Got it. So it seems like we could tell our user (the stripe account owner in this case) that if they want these charges to come into our system, then they must have an email set somewhere, depending on how they created their customer.

I guess I just assumed that there was naturally always an email available when a stripe charge happens, but apparently there are ways for charges to happen without it.

I think we've fixed my original issue a few days ago.. that was getting the email for Stripe Checkout scenarios... we're getting that from billing_details now.

Thanks again

lunar sorrel
#

yeah email is definitely optional so it depends on a lot of factors sadly

#

and I'm glad you figured out the Checkout bits. It's definitely hard to build a platform like yours where you have to adapt to all the quirks of the dozens of integration paths we have

spark estuary
#

Curious... Since it was in the charge.description as "Charge for <email>" .... is there any way to see how that got there?

lunar sorrel
#

what's the charge id? 🙂

spark estuary
#

ch_3M9whnGlB3V4SWCZ0YHz04FE

lunar sorrel
#

You can look at their Dashboard, you can see that Charge, you can see the request logs and see who created it

#

another platform created that payment and explicitly passed that description in the API

spark estuary
#

I can't see their dashboard... I can retrieve objects via api since they have oauth'd with us

#

ok, that answers it

lunar sorrel
#

you can see their Dashboard though

spark estuary
#

oh... cool, how?

lunar sorrel
#

if they are connected to your platform, you have a page for their account in your own Dashboard and then a way to view their Dashboard from there

spark estuary
#

interesting... I'll try to find that.... I mean, I thought all we had was an oauth token for them.... I don't think it's a "connected" account in the formal sense

#

as in Stripe connect/express/etc

#

If I search in my dashboard search box for the email, charge, ca_xxx application id, etc nothing comes up

lunar sorrel
#

yeah none of those make sense 😅

#

and you can load the right one (you should know the id of that account acct_123)

spark estuary
#

ahhh, that's it needed to search by acct_

#

Thanks again, this has been most helpful

lunar sorrel
#

Of course 🙂

spark estuary
#

and now that I can see the other 3rd party they're using... it helps to know that's how they are doing charges and I might be able to account for it

lunar sorrel
#

🙂

spark estuary
#

Alright... I'll let ya go. Thanks again!