#sl_api

1 messages · Page 1 of 1 (latest)

outer novaBOT
#

👋 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/1219964094405279746

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

main dewBOT
hardy oriole
#

hi! to be honest I don't know what a "advance_funding transaction" is. Do you have a bit more context?

narrow nimbus
#

I actually think it came from an error on Stripe where it accidently sent funds to payout sooner than they should have been - I'll see if I can find the email

#

WF4PN51MW

#

that is the reference identifier from the email we were sent

#

Stripe Connect destination charges [0] made between 2024-02-13T00:44:00 UTC and 2024-02-13T15:50:26 UTC were initially processed and made available today (T+0) instead of the payout schedule your platform set.

Stripe has identified the source of the issue and we have remediated it. Payout schedules for your connected accounts have been restored and funds from destination charges made between 2024-02-13T00:44:00 UTC and 2024-02-13T15:50:26 UTC will be paid out as originally intended. You will notice two additional Balance Transactions per impacted Balance Transaction in your Payout reconciliation reporting that will be made to ensure these funds are paid out as intended. Please see below for an example:

  • Balance Transaction 1: the original, incorrect T+0 balance transaction
  • Balance Transaction 2: a negative balance transaction, offsetting the original ‘Balance Transaction 1’
  • Balance Transaction 3: the correct transaction according to your platform’s payout schedule

If you have any questions, please reply to this email.

hardy oriole
#

can you reply to the email instead please?

#

I know zero about this

narrow nimbus
#

ok but can you tell me how to look upt the details of a py transaction

hardy oriole
narrow nimbus
#

do I need to pass in the connected account on the retrieve as its not finding it

hardy oriole
#

you do yes

#

that py_ represents the arrival of a Transfer into the connected account and as such is an object on that account and you would pass the Stripe-Account header on requests to retrieve it

narrow nimbus
#

Yes we already use that flow to reconcile payouts - but these transactions are unusual

#

is stripe_account the correct value to pass to the charges->retrieve method as its giving me Status: 400 Type: invalid_request_error Message is Received unknown parameter: stripe_account

hardy oriole
#

you don't pass it as a parameter you pass it as an option

#

$x = \Stripe\Charge::retrieve(['id' => "py_xxx"], ['stripe_account'=>"acct_xxx"]); I think it's like that in PHP

narrow nimbus
#

$x = $stripe->charges->retrieve(['id' => $chargeId], [
'stripe_account'=>$paymentMethod->account_no
]);

gives error
trim(): Argument #1 ($string) must be of type string, array given

when I try
$x = $stripe->charges->retrieve($chargeId, [
'stripe_account'=>$paymentMethod->account_no
]);
Status: 400 Type: invalid_request_error Message is Received unknown parameter: stripe_account

hardy oriole
#

$stripe->charges->retrieve( $chargeId, [
'stripe_account'=>$paymentMethod->account_no
]);

#

or if that doesn't work it's something like this

#

$stripe->charges->retrieve( $chargeId, [], [
'stripe_account'=>$paymentMethod->account_no
]);

narrow nimbus
#

thank you the second one worked