#avery246813579

1 messages · Page 1 of 1 (latest)

atomic plumeBOT
haughty cypress
#

Also an indication of what balance you're referencing from the Dashboard. I'm looking and don't see a pending balance for that account

final lynx
#

const balanceTransaction = await stripe.balanceTransactions.retrieve(
'txn_3OjKXPAcqRxm04BK16DGlp6q'
);

#

Pending balance transaction which should indicate pending balance

#

Date available is tonight as well

haughty cypress
#

I think that is flagged 'pending' in that it was included in the payout for that account that was created today: po_1Oj9wGPI8qo6RQxL8Ayyp0RP

#

i.e. it's already left the Stripe balance

final lynx
#

I don't believe it should have

#

And it should be available if that was the case

haughty cypress
#

That's what it looks like for that txn_xxx you've just sent me. I can see the disbursement record for the payout

haughty cypress
final lynx
#

Then there is a massive bug

#
{
  id: 'txn_3OjKXPAcqRxm04BK16DGlp6q',
  object: 'balance_transaction',
  amount: 4025,
  available_on: 1707868800,
  created: 1707825194,
  currency: 'usd',
  description: "Hometown Grounds's Register Order",
  exchange_rate: null,
  fee: 0,
  fee_details: [],
  net: 4025,
  reporting_category: 'charge',
  source: 'ch_3OjKXPAcqRxm04BK1OgqDvq7',
  status: 'pending',
  type: 'charge'
}
#

Status should be available when it's been paid out

#

If it was sent in a payout before it was available that's a massive issue

#

I can give you every balance transaction that was in the payout from yesterday, and that payment was not

haughty cypress
#

Hmm, I think I was mistaken there re:payout. Apologies

#

Looking further

final lynx
#

I think it's displaying pending payments as available

haughty cypress
#

Wait, txn_3OjKXPAcqRxm04BK16DGlp6q is for a different account to what you shared originally: acct_1Au9cPAcqRxm04BK

final lynx
#

That's the merchant account

haughty cypress
#

Yes, so why would it settle on acct_1OXEd4PI8qo6RQxL?

final lynx
#

We transfer into it's account

#

I can find you the transfer ID

#

tr_3OjKXPAcqRxm04BK1xBPblj6
py_1OjKY3PI8qo6RQxLj3TITx3t

#

I store all of this very granularly

#

Very interesting

#

txn_1OjKY3PI8qo6RQxLH7V2qq3y for acct_1OXEd4PI8qo6RQxL is instant availability

tall granite
#

Hi there 👋 jumping in as my teammate needs to step away. Please bear with me a moment while I catch up here.

final lynx
#

Sup Toby

#

You're in for not a fun time

#

I think someone might have fucked up payment availability code

#

Sometime last night

tall granite
#

Well that doesn't put me in a great mood...

final lynx
#

It doesn't put me in a good mood either

tall granite
#

Sorry, there are a lot of object and account IDs flying around, trying to parse what you're describing

final lynx
#

Yeah I understand

#

We have very very detailed records of transactions and payments and we validate our records on Stripe records

#

The customer has the available funds which should be pending according to balance transactions and the available date

tall granite
#

The Connected Account has the available funds? (Customers are something different, I'm trying to be very explicit to keep things straight in my head)

final lynx
#

Yeah

#

The funds are in the available balance instead of pending

#

This is just one out of 150+ mismatches we got this morning

tall granite
#

Let's start with one specific example. How exactly are you checking the balances, and where is the mismatch you're seeing? (Preferably ignoring what you're seeing in the Stripe dashboard because we in this forum aren't too familiar with how it decides to display balances and instead focus on working with our API)

final lynx
#

Sure

#

Let's look at acct_1OXEd4PI8qo6RQxL

#

Oh damn this fucked fucked

#

available: [ { amount: 22452, currency: 'usd', source_types: [Object] } ]

#

It just keeps going up

#

Did someone give us T+0

#

All of these should be in pending balance

#

txn_3OjKXPAcqRxm04BK16DGlp6q
txn_3OjKcHAcqRxm04BK0HQtGY84
txn_3OjKhXAcqRxm04BK0yiXZxDk
txn_3OjLAIAcqRxm04BK0qTVDf35
txn_3OjLHGAcqRxm04BK0b5SAx9a
txn_3OjLITAcqRxm04BK0JJcEY9K
txn_3OjLQSAcqRxm04BK0a0X02us
txn_3OjLVVAcqRxm04BK0AMv8hgc
txn_3OjLZ1AcqRxm04BK1mtXV9TB
txn_3OjLfwAcqRxm04BK0L9fjtvX
txn_3OjM35AcqRxm04BK0ilWHJlQ
txn_3OjMtWAcqRxm04BK1euJeCn8
txn_3OjN2SAcqRxm04BK0Mcz0ATV

#

All of these are platform account balance transactions with balance of pending, which should be reflecting on the connect account as pending as well

tall granite
#

Okay, this is for a Destination Charge flow

final lynx
#

Correct

#

Let's look at txn_3OjN2SAcqRxm04BK0Mcz0ATV

tall granite
#

Alright, let me close what I had, I picked a different one

final lynx
#

Here is the source, payment, and transfer associated with it

#

ch_3OjN2SAcqRxm04BK0yHyeGKu
tr_3OjN2SAcqRxm04BK0Uen4u7R
py_1OjN2ePI8qo6RQxL9zStwVIt

#

Here is the balance transaction (txn_1OjN2ePI8qo6RQxLcmjaEQ2G) on the connect account (acct_1OXEd4PI8qo6RQxL)

#
{
  id: 'txn_1OjN2ePI8qo6RQxLcmjaEQ2G',
  object: 'balance_transaction',
  amount: 2040,
  available_on: 1707834780,
  created: 1707834780,
  currency: 'usd',
  description: null,
  exchange_rate: null,
  fee: 64,
  fee_details: [
    {
      amount: 64,
      application: 'ca_EcYucyx70vKGw95j60oFUzTsapjCKSLo',
      currency: 'usd',
      description: 'Dripos application fee',
      type: 'application_fee'
    }
  ],
  net: 1976,
  reporting_category: 'charge',
  source: 'py_1OjN2ePI8qo6RQxL9zStwVIt',
  status: 'available',
  type: 'payment'
}
#

This should not be instant access to funds, it should coordinate with the balance transaction from the platform account

#

This account is now getting T+0

#

This changed overnight btw

#

It was working the other way yesterday

#

I could honestly find a certain time and you could probably find a PR that coordinates with it

#

Most recent transaction on our side

#

acct_1N2jKCPDPZnpXkPt

tall granite
#

please, let me look into one

final lynx
#

SOrry

#

This is just kinda sev 0 bug right now

#

I got a time it changed if you'd like it as well

tall granite
#

What is the full object structure you see for txn_3OjN2SAcqRxm04BK0Mcz0ATV?

final lynx
#

Okay this is confirmed fucked

#

I am going to reach out to urgent support

tall granite
#

that's probably a better idea if this is urgent (in the future, I'd also recommend less f*** in your message, I know it certainly soured my mood as soon as I joined the thread)
I'm trying to see if a teammate has time to look into this as well

final lynx
#

Well this is a massive bug on Stripe side

#

This shows you exactly what you need to know

#

Anything after 1707785742240 is now instant availability

languid zephyr
#

Hello

final lynx
#

You are allowing our customers to withdraw money before the balance transaction is available on the platform side

languid zephyr
#

Pause for a second in providing more information

#

I'm looking

final lynx
#

Look at the text file

#

That has everything you need

#

And the objects as well pulled from Stripe

languid zephyr
#

Okay I'm escalating internally, hold tight.

final lynx
#

I have a urgent inquiry and one with our dedicated support

#

But you see this is very messed up as well correct?

languid zephyr
#

It does look like the funds on the Connected Account are becoming available before they should be, yes.

final lynx
#

That is very much not good if I do say so

#

I guess we are lucky that we built an internal audit system for this exact reason lol

languid zephyr
#

Thanks for flagging this. We are investigating internally

#

Any idea what the earliest balance transaction you saw this behavior with is?

final lynx
#

Yeah I can get you an exact time

#

I know between 1707785742240 and 1707786078084

languid zephyr
#

That's helpful, thanks

final lynx
#

I can get a more exact time

#

After 1707786030588

#

After 1707786044715

#

In between these two timestamps

#

1707786067651
1707786078084

languid zephyr
#

Thanks, we have several folks investigating. I'll circle back with an update as soon as I have one.

final lynx
#

Thank you

#

I am getting spam texted with alarms on our end and over 300+ connect account balances are messed up, so just want to stress the urgency of this

languid zephyr
#

We have opened an incident and are investigating as rapidly as possible.

final lynx
#

Getting those platform balance transactions updated to have the correct available date would be epic

#

Awesome thanks

#

Do you know if the scope is just isolated to my account, or is it with destination charges across all accounts?

languid zephyr
#

Across all accounts. Believe we have identified the culprit of the bug and it should be fixed for new balance transactions going forward shortly.

final lynx
#

Oof

#

Hate to be a T+2 platform account with express today

languid zephyr
#

Okay issue should be resolved for transactions going forward.

#

I've tested and am seeing that from my end. Can you also pull a latest balance transaction from your end just to confirm?

final lynx
#

Yeah let me look

#

Was I the first person to bring this up?

languid zephyr
#

As far as I know, yes

final lynx
#

lol

#

I am sorry for being angry

#

I know it is not your guys fault

languid zephyr
#

I understand that you are/were upset

#

Totally reasonable

#

Just speaking on here in an angry way won't get you help faster

final lynx
#

Yeah I understand that

#

Just not a good thing to wake up to 250+ connect accounts having bad standing in our system

languid zephyr
#

Yeah I agree. Sorry you had to deal with this -- I definitely appreciate you coming here and reporting it.

final lynx
#

Alright showing pending now

#

Can we get the balanace transactions on the connect account back dated?

languid zephyr
#

Yeah there is discussion in the works already about fixing affected balance transactions.

#

I can't guarantee here that will happen though and I don't know how it will line up in terms of those balance transactions that were already paid out

final lynx
#

None of them should have been paid out on our end

#

hopefully at least

#

We had one payout that would have been affected po_1OjN1HPHqGdmUawmJb7DNQ64

languid zephyr
#

You said you do already have an open ticket with our Support team?

final lynx
#

Yeah but they said stay here lol

#

Which is confusing

#

Since you usually say stay with support

#

I can bump in the thread

#

It's in support escalation

languid zephyr
#

Yeah at this point you are going to just want to correspond over email for what happens in terms of the remediation.

#

It is going to be more async at this point and I won't be monitoring that.

#

So for any specific questions about the remediation I'd recommend you include it over email and they can then correspond with our Eng team that is working on the remediation items.

final lynx
#

Awesome

#

Thanks for all the help