#ednonstop
1 messages · Page 1 of 1 (latest)
You'd get it from the related Payment Intent object: https://stripe.com/docs/api/payment_intents/object#payment_intent_object-charges
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
That link probably won't work as we just removed that field in a new API version
But it'll be there in your API responses assuming you're on 2022-08-01 or earlier
Okay, here is
var charge = await stripe.charges.retrieve(
'ch_3LAdSVCsmBaUST9m0Bjkkgor',
What is this id? And how to get it? There is no charge object inside payment intent response or i'm missing something
Also i'm already using updateCharge request but charge_id there is destination_payment from transfer. Too confusing
Can you share the Payment Intent ID you're working with? pi_xxx
payment intent id which shown me in api docs is
pi_3M5XkKCsmBaUST9m0VE5lNq5
but i can share last created id from my stripe panel
Can you share a pi_xxx that has actually been processed successfully and you're attempting to create a transfer from?
Okay
pi_3M6afvCsmBaUST9m0J0VzXQm
After it's created it has an attempt to transfer and error Insufficient funds in Stripe account and every payment took 7 days to fully deposit to account. So stripe support reccomend to use source_transaction to make it fast
This is a main problem we have in live mode.
you can access the charge ID ch_xxx there by doing payment_intent.charges.data[0].id Did that not work ? what code did you try?
Yes i just saw this in response log in stripe panel, but this is not visible in docs here https://stripe.com/docs/api/payment_intents/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.
maybe that's why it was a bit confusing
it's because the API docs are for the latest version and in the latest version charges was deleted
but yes I can see how this is confusing
So can you confirm that if i'll implement source_transaction then the funds will be deposited fast into owner account and transfers will work normally as fast as they must?
because now every payment we must wait 7 days
This issue is in live mode.
it doesn't change anything about when the payout happens, that would still take the same amount of time,
it just means you can transfer the funds to the connected account without waiting; the funds then just 'sit' in the connected account and will be paid out when they're available e.g. after 7 days.
Okay. We have a problem not about payout to the connected accounts, but about Incoming to Stripe
Now it is:
Transactions available by 28 November 2022
And we have zero balance because of this and nothing to transfer :/
What's the solution?
not sure, I don't have access to your account or context on what this "incoming to Stripe" balance is.
Will be available in Stripe soon
This amount is estimated because transactions are still accumulating.
that is a string from our dashboard yes
- transactions are still accumulating
I have no idea what account it relates to though
is there more context/screenshots/object IDs/failed requests you can share?
No failed requests, just stripe asking to wait 7 days after payment in live mode
Stripe support recommend to implement source_transaction but you'r saying it's about payouts to connected account's so it's for another purposes
source_transaction is for allowing you to transfer the funds to the connected account without waiting; the funds then just 'sit' in the connected account and will be paid out when they're available
Okay, this may be a solution
they still take as long as they take per https://stripe.com/docs/payouts#payout-speed
the first payout to an account takes 7 days(the funds are not available for 7 days)
Anyway my requests and full flow will be succeeded if i implement source_transaction. But funds still will appear in 7 days for this time
yes