#alex2_api
weak sandalBOT
👋 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. Thank you for your patience!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
🔗 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/1213273722996400178
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
crude rivetBOT
obtuse zodiac
Hi, what do you mean by 'ChargeSearch to match the receipt with the charge'?
thin nova
Hi I first search with the mail of the customer with https://docs.stripe.com/api/customers/search and then use the custID to search the charges https://docs.stripe.com/api/charges/search. The charges result includes a receipt ID (if it was sent to the user)
in the case of 100% discount coupon, there is not "charge". My users still get a receipt ID which I dont know how to query in the stripe API
obtuse zodiac
So you just want to know what the receipt number?
thin nova
in the first case of the charge, I can confirm with the chargeSearch that the selected receipt is linked to a payment intent which I also store locally. So it's an easy way for me to confirm ownership
in the second case with the promo code, I have no way to link that receipt they get to anything.
obtuse zodiac
I think the best way to track these on your end is to add metadata, https://docs.stripe.com/api/metadata instead. As you scale, using the Search API functionality is not going to be ideal as you might hit rate limits, https://docs.stripe.com/rate-limits.
So when you create the payment, you can pass in a key value pair, and store information on there to later track.
With 100% discount, there is no charge but an invoice is created for $0 amount. For this reason, you could link that to the invoice. However, I do think using the metadata is going to be best for tracking purposes.
thin nova
nice I'll have a look. However when I checked my dashboard, no invoice was created. When I go to invoices I get the starting screen to create invoice
obtuse zodiac
Can you share the request id that you used to created the subscription with 100% off? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
thin nova
req_7LyhUavRBY0IP7
obtuse zodiac
That is the request for creating the promotion code
obtuse zodiac
Ah, you mentioned saas application so I assumed you were creating a recurring charge
Can you share the request for the one time payment then where you applied the 100% discount?
thin nova
req_7LyhUavRBY0IP7 should be it. This the req that go triggered when I applied it
the event after this request is the checkout session
obtuse zodiac
That is the request to create the promotion. I suspect that you're not passing, https://docs.stripe.com/receipts?payment-ui=checkout#paid-invoices so invoice is not sent. So yeah, stepping back you should use the metadata to track this on your end. That would be much more efficient.
thin nova
ok, assuming I pass that metadata, how can I programmatically query for those metadata? Wouldn't I be usingh the searchAPI again?
obtuse zodiac
It looks like you're using Checkout so you can listen to checkout.session.completed event and setup webhok, https://docs.stripe.com/webhooks. Then, you can store all of that information on your end.