#emmanuel-lambert_api

1 messages ยท Page 1 of 1 (latest)

raven bronzeBOT
#

๐Ÿ‘‹ 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/1350030542376276050

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

lyric solstice
#

๐Ÿ‘‹
I'm not able to open the requestId req_s9BcVQCYHzhk3h is there a typo in it ?

#

Also do you have automatic payouts activated ?

raven bronzeBOT
dense moon
#

yes I have automatic payout everyday

boreal inlet
#

๐Ÿ‘‹ taking over for my colleague.

boreal inlet
#

ok

#

yes requests IDs are case sensitive

#

ok since you're creating the transfer after a few days the payment you're passing, and the source of the transaction has already been paid, we won't be able to fund the transfer from that payment

#

and you're basically having an insufficient funds

dense moon
#

the payment is received few seconds before the transfer only the invoice is 10 days before

#

for example for invoice in_1Qxe9JEj4rNYzxWGv4qVs7iq

boreal inlet
#

ok taking a look

boreal inlet
#

I'm sorry it's taking so long, I'm trying to get to the bottom of this issue

dense moon
#

no pb

boreal inlet
#

ok so basically the invoice that was paid had a balance transaction txn_3Qxee9Ej4rNYzxWG0givlTse that was part of the payout po_1R1GbGEj4rNYzxWGixxQenyv on March 11th

raven bronzeBOT
dense moon
#

yes we first invoice and then transfer

vast coral
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away.

#

When using source_transaction, the Transfer is only created against that Charge if the payment hasn't already settled. In this case it appears that payment had already settled, so the funds from it had already been attributed to your balance, so we checked against your account's balance rather than the source_transactions funds (since they'd already been released into your account and could no longer be reserved).
https://docs.stripe.com/connect/separate-charges-and-transfers?platform=android#transfer-availability:~:text=With a source_transaction%2C the transfer request returns success regardless of your available balance if the related charge has not settled yet.

It's also worth noting that we typically don't recommend using source_transaction with async payment methods, like Sepa that was used here, due to the behavior we discuss in this section:
https://docs.stripe.com/connect/separate-charges-and-transfers?platform=android#transfer-availability:~:text=Asynchronous payment methods,manage payment failures.

dense moon
#

ok, thanks I'll look into that