#mckeemi_api

1 messages ¡ Page 1 of 1 (latest)

hazy frigateBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1308370741955133522

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

mortal marsh
#

hi there!

mental crow
#

Hi Soma

mortal marsh
#

correct, the API can only list real customers, not guests customers

#

can you share a specific PaymentIntent ID with an email address you are interested in?

mental crow
#

Sure let me get one

mortal marsh
#

yes I confirm pi_3QHOZGJIye6pnJ5a1jMyI5wA this is using a guest customer

#

(I just deleted your message to hide the email address, since this is a public channel)

mental crow
#

apologies, I should have used a mailinator email address, thank you for deleting.

#

Just to confirm, there is no way around this, I'll need to use our own data instead of going direct through the API in this instance?

#

If I list all the paymentintents is there a way of displaying the email address associated with the payment?

#

Will that come back in the list?

mortal marsh
#

having a look

mental crow
#

Thanks

mortal marsh
#

looks like the email is stored in the description field of the PaymentIntent, so at least you could get it like this.

hazy frigateBOT
mental crow
#

yes thank you, I can see that when you open the payment on the dashboard there is a Charged to 'email address', does this value come from somewhere? Maybe if I get the list of charges instead?

rugged slate
#

no, that's our concept of a "guest customer" and it's not in the API at the moment. The idea is based on the IP address/card fingerprint we 'think' it's a payment from an existing customer with that address

#

looking at it though it seems like nonsense or it doesn't work for the way your payments are setup so I'd kind of ignore it

#

ah it 's because it's test mode, so everyone has the same card. I suppose it works better in live mode

mental crow
#

ah ok, that's fine, I can work with the data we capture when the payment was created and filter on email there as opposed to going direct to the api

rugged slate
#

or as you say, if you have it in the description field of the PI you can parse it out from there too