#red_api
1 messages · Page 1 of 1 (latest)
👋 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/1435688294297108611
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- red_api, 13 hours ago, 97 messages
- red_api, 1 day ago, 25 messages
- red_api, 1 day ago, 9 messages
- red_integration-security-checklist, 1 day ago, 6 messages
- red_api, 5 days ago, 87 messages
Hi there,
do you have a request ID for me?
Or an account ID and I can try to find one?
the document shows that it's not even supported yet in node.js
Oh yeah. That is true. Sorry about that. The API is relatively new .
which is a huge gap given I've started using the API
what do you suggest as a workaround?
Hi, taking over as my teammate needs to step away. Let me catch up.
Hi
Did you try using this beta, Node.js SDK 19.3.0-beta.1 version: https://docs.stripe.com/api/payment-record/retrieve?api-version=2025-10-29.preview&rds=1 ?
Ummm no - first time seeing it
Is it production ready?
That’s still showing curl for me?
Given that it's new, it's likely that it would not be documented yet. It is in a preview and you can look at what that means here: https://docs.stripe.com/release-phases.
Yes, you should be able to access it: https://github.com/stripe/stripe-node/releases/tag/v19.3.0-beta.1
"We show the cURL request because this method is currently unsupported in the Node.js client. To see it in the library, let us know about your use case."
Let me look further and test this on my end as well. Since this is new, I have not played with it just yet.
ok thanks. I don't see anything in the release notes regarding it
Actually, I'm wrong.
This is GA-d with https://docs.stripe.com/changelog/clover/2025-10-29/payment-records
This was GA-d as of last week so with this version, https://docs.stripe.com/changelog/clover/2025-10-29/payment-records#upgrade it should work.
Can you try this please?
sure
i'm on 10-29
where do I see the format of the retrieve payment record call?
I'm expecting something like
stripe.paymentRecords.retrieve
it doesn't auto-complete in my editor fwiw
Yeah, it should look something like that: stripe.paymentRecords.retrieve
Let me know if that did not work
have to refactor a little to try it
"errorType": "TypeError",
"errorMessage": "Cannot read properties of undefined (reading 'retrieve')",
"stack": [
"TypeError: Cannot read properties of undefined (reading 'retrieve')",
" at handleQuery (file:///var/task/index.mjs:114:61)",
" at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at async Runtime.handler (file:///var/task/index.mjs:32:16)"
]
}```
for code:
var paymentRecord = await stripe.paymentRecords.retrieve(paymentRecordId);
Can you try https://docs.stripe.com/api/payment-attempt-record/list please as a work around?
I'm still looking as our document states 'Retrieve' is added for that endpoint: https://docs.stripe.com/changelog/clover/2025-10-29/payment-records?changelog-sdk=node#upgrade
Are you able to write in 'to see it in the library, let us know about your use case.': https://docs.stripe.com/api/payment-record/retrieve please?