#peililintu-payout
1 messages · Page 1 of 1 (latest)
it's what we use to charge service fees I believe
for example the pricing for using Billing or active accounts in Connect or Radar screening fees, are charged as adjustments to your account, and I believe binvp_xxx are used as part of that
if you can find it on https://dashboard.stripe.com/balance filtering by 'Stripe Fee' that usually makes it clearer
Our periodic process basically (i) fetches recent charges and payouts; (ii) fetches the transaction details for each payout; (iii) saves any charges we haven't seen before (in our local system); (iv) updates existing charges with the amounts from payouts (now that we now how much was actually paid/received).
So the problem occurs in step (iv): we are told about these "binvp" amounts being "paid out", but there was never an associated charge, so our system can't find the record to update.
We've never had this issue before in all these years, so I'm trying to understand what is different in this situation.
like I said they're fees for services so they probably don't have any particular source_transaction for the BalanceTransaction, so your code should try to robustly handle that
We do regularly pick up fees for services through the API though. In this case I noticed that the binvp stuff cancels out to zero, as it appears a fee was charged and then refunded -- could this be related, or perhaps just coincidence?
Stripe fee (£0.27) [...] Card payments (2022-05-08): adjustment to Credit for previously-assessed fees 18/05/2022
Stripe fee £0.27 [...] Card payments (2022-05-08): Credit for previously-assessed fees 17/05/2022
sounds like we probably charged you a fee and then refunded it due to a billing mistake or something
if you're on advanced interchange pricing this might also be a 'true-up', I'm not sure. Ultimately if you have specific questions about specific transactions on your account https://support.stripe.com/?contact=true can help more than an anonymous Discord channel!