#ajacombs_api
steep fogBOT
👋 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/1361531377144697074
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
stuck hatch
hello! taking a look, gimme a while
where did you find this report type exports.unified_payments from?
umbral isle
It's listed as one of the report types in the response from https://api.stripe.com/v1/reporting/report_types. I recognised the name from having looked at the network traffic when exporting the CSV from the transactions page of the web UI to see if I could identify where that was coming from.
stuck hatch
so if I understood this right, you were taking a look at the network requests from our dashboard and then found that report type and tried using it?
umbral isle
That's right, as with all the other parts of the API I've tried to use, I couldn't find a way to know the terminal reader ID associated with a transaction. But I knew it was there somewhere, as it is visible in the web UI and in manual CSV exports from the web UI.
stuck hatch
so I don't recommend using a undocumented report type. There's no guarantee that we won't change the name or details in it.
If you really want to include the terminal reader ID associated with a transaction, what I would recommend you do instead is to update the Charge or PaymentIntent with metadata that includes the terminal reader ID after payment is completed
umbral isle
For context, I work for a public transport agency which has Stripe readers deployed on a small fleet of buses servicing our airport route to allow paying by credit card / EMV, as our main ticketing solution deployed on the rest of the bus fleet does not currently allow paying by credit card / EMV. We now want to take this data to calculate patronage of passengers paying via Stripe to add to our data warehouse. We would ideally like to avoid changing the existing Stripe integration done by our ticketing vendor (such as by getting them to add terminal reader ID to the payment intent metadata), and instead just consume the data that's already there. Especially as presumably if we did start adding terminal reader ID to the payment intent metadata, that would only apply going forward, and we want to consume data looking back as well.
Is there no documented way to access the terminal reader ID of a transaction (/charge / payment intent) via the API? Other than by having added it to the metadata?
[also thank you for your help, I really appreciate it =)]
stuck hatch
can you share an example PaymentIntent id which I can take a look at?
umbral isle
Sure thing, pi_3RE02CEe9iZkNQu30GalO2lS is from ~20 minutes ago
stuck hatch
Is there no documented way to access the terminal reader ID of a transaction (/charge / payment intent) via the API? Other than by having added it to the metadata?
not that I'm aware of off the top of my head right now. Gimme a while more to ponder over this
If you don't mind, can you write in and we'll get back to you via the support ticket. I'll share a link with you where you can create the ticket - you should be logged into your Stripe account
steep fogBOT
Hello @umbral isle, we have sent you a direct message, please check it at https://discord.com/channels/@me/1361551000334368859
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
umbral isle
All good, I've done that now.
stuck hatch
alright thanks! we'll let you know via the ticket. I'll be closing this thread shortly so if you have another question, feel free to start a new thread