#yi_code

1 messages · Page 1 of 1 (latest)

naive harnessBOT
#

👋 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/1406911299706814525

📝 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.

  • yi_code, 9 minutes ago, 4 messages
halcyon shore
#

👋 Hi there! I'm taking a look at this for you

#

As you note, with the Basil API version, we removed the paid_out_of_band property from an Invoice

bronze elbow
#

Yes

halcyon shore
#

To retrieve the paid status, you can also look at the status attribute of an Invoice, which would be paid

#

There are a couple of options to determine the "out of band" status for an Invoice:

#
  1. Retrieve the Invoice using an API version older than 2025-03-31.basil — as the paid_out_of_band field will still exist
#
  1. With the latest API version, you can check whether an invoice is paid but has no associated InvoicePayments (payments attribute)
bronze elbow
#

Thanks, we are going to upgrade to 2025-06-30.basil

#

And the paid_out_of_band field was definitely removed.

halcyon shore
#

Yes, that's correct.

#

To explain option #1, it's possible to make individual API calls using an older version of the Stripe API. So if you really need to rely on the paid_out_of_band attribute, you have the option to retrieve an Invoice with an older API version

bronze elbow
#

I will try the option #2 and make an experiment on Stripe Dashboard

#

I think the option #1 is good, but my team wouldn't approve it

halcyon shore
#

There another possibility is mentioned: you could use metadata to store the "out of band" status on the Invoice

bronze elbow
#

I'm afraid not because these invoices(out of stripe) always were handled by our biz team. And they don't know what's the metadata.

halcyon shore
#

Are you using the Stripe Dashboard to mark invoices as out-of-band payments?

bronze elbow
#

Check finished. I have to say: it's so troublesome for this breaking change.