#okg
1 messages · Page 1 of 1 (latest)
Do you have the example Balance Transaction object I can look at to see this behavior myself?
py_1MoBzEFcGlj86sWxw29vkxXo
I don't personally have access to the txn object right now
I need the txn object you're looking at so I can verify the behavior you're seeing.
[{
"id": "txn_1MoBzEFcGlj86sWxgapsN8Yl",
"connected_account_id": null,
"payout_id": null,
"amount": "3421",
"available_on": "2023-03-29 00:00:00.000000 UTC",
"created": "2023-03-21 20:40:52.000000 UTC",
"currency": "usd",
"description": null,
"exchange_rate": null,
"fee": "50",
"net": "3371",
"source": "py_1MoBzEFcGlj86sWxw29vkxXo",
"status": "pending",
"type": "payment",
"source_account": "..."
}]
Server is busy, will circle back in a few
ty
Did you just retrieve this? Or is this from an old retrieve event?
This is current from our data warehouse. So that could have an issue, I'd be interested to know if you see different data on your end?
And/or if the "available_on" field is ever updated (for instance, if funds land sooner than originally written)
I would recommend doing a quick retrieve call to get the current state of the transaction and compare that against what's in your database. I'm not sure if/when these fields get updated and I can't unfortunately see that granular of detail about them
Gotcha. Do you know if there's any more detailed documentation on status or available_on beyond what's in https://stripe.com/docs/api/balance_transactions/object ?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.