#louis_balance-trx
mortal jacinthBOT
👋 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/1245659253713408010
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
torpid rover
Hi
I think you are looking at the. available_on field:
https://docs.stripe.com/api/balance_transactions/object#balance_transaction_object-available_on
ancient gull
Would that field be set on the correct value even if the bank sends the funds late?
torpid rover
Yes I think so, because the amount will be available in your Balance only when received
ancient gull
Ok I was confused by the wording "become" and here I understood that the value wouldn't change ("The Balance Transaction available_on dates will remain constant throughout this change."), implying that the field value is known when the payment is created
But now I think it just meant that during the migration process, available_on wouldn't change for existing payment?
Thanks
hollow vault
👋 taking over for my colleague. Let me catch up.
I think you're confusing two concepts
the Stripe Balance availability and the Payout date
the Stripe Balance availability is when the amount will be available in your Stripe Balance
ancient gull
Yes I am talking about stripe balance availability (customer funds -> Stripe balance), not payment date (Stripe balance -> our bank account)
hollow vault
ok perfect
then as my colleague suggested the available_on field is the one you're looking for
ancient gull
Is there a maximum delay between balance_transaction.created and balance_transaction.available_on?
Like if it takes too long it is marked as failed and funds will be refused by stripe afterwards if they still arrive?
Or, better, is there a way to fetch balance transactions where available_on is is the past?
hollow vault
Is there a maximum delay between balance_transaction.created and balance_transaction.available_on?
it depends on the LPM
Like if it takes too long it is marked as failed and funds will be refused by stripe afterwards if they still arrive?
if the charge has succeeded this won't happen
and if you're using the latest API version you'll be using by default the automatic_async capture method which is explained here https://docs.stripe.com/payments/payment-intents/asynchronous-capture#opt-in-async-capture
ancient gull
> Is there a maximum delay between balance_transaction.created and balance_trans...
Sorry I don't know what LPM is?
hollow vault
LPM = local payment methods
ancient gull
LPM = local payment methods
Concerning SEPA debit do you know this delay?
ancient gull
Even after https://support.stripe.com/questions/changes-to-balance-transaction-behavior-for-debit-payment-methods?locale=en-US ? We received an email about this and SEPA debit
hollow vault
sorry I meant won't be available
ancient gull
Ok, thanks for your answers, I'll try to find a solution
hollow vault
what are you trying to solve?
ancient gull
Our accountant wants invoices only for payment that are in the Stripe balance, so we have to manually create invoice serial numbers for only the payment that are in the Stripe balance (instead of when the payment is created). Before the "Changes to Balance Transaction behavior for debit payment methods", we could reliably create this because every balance transaction created was indeed available in the balance transaction.
Now I think I will have to add a delay that could be variable when payments take longer, but this will delay all other invoices
(these invoices are thus internal to our system, we don't use Stripe Invoices)
hollow vault
you can just filter those that don't have any available_on
ancient gull
Yes and I would keep in memory the earliest "pending" invoice
mystic parcelBOT
ancient gull
Filtering instead of waiting would need some code refactoring and e already add a static delay of 14 days before invoice creation because of another legacy payment provider, so I'll just wait for balance transactions to be available and we'll assess from there 🙂
Last question : before the "Changes to Balance Transaction behavior for debit payment methods", would balance_transaction.available_on always be equal to balance_transaction.created ?
lapis fern
yes
ancient gull
Thanks
mortal jacinthBOT
ancient gull
Does this impact balance transactions of reporting category "refund" too? (will the available_on property be != created?)
lapis fern
no it's only for the BT associated with the payment