#bwurtz999_api
scenic karmaBOT
👋 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/1306285696201265224
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bwurtz999_api, 52 minutes ago, 32 messages
vast spireBOT
viscid mist
Hi there 👋 just to make sure, that was a request made from our stripe-terminal-android SDK, correct?
long ferry
Yes I believe so
Also - I can't figure out why some requests are using a 2020 version (req_N1G7y4RzrMGPTg)
$stripe = new \Stripe\StripeClient([
'api_key' => config('services.stripe.sk'),
"stripe_version" => config('services.stripe.version')
]);
This is how I set all StripeClient on the server side
and services.stripe.version is a 2023 version
viscid mist
These are client-side requests, how you initialize your server isn't relevant.
long ferry
Oh OK. Does the reader need to be updated?
viscid mist
The second one you linked, req_N1G7y4RzrMGPTg, is from an Elements integration, and is a call that our library makes on it own. It's using the default API version for your account. I'm pretty sure that one can be adjusted when initializing Stripe.js:
https://docs.stripe.com/js/initializing#init_stripe_js-options-apiVersion
I need to take a closer look at whether you can specify a particular API version when using stripe-terminal-android
long ferry
OK thank you
long ferry
I need to take a closer look at whether you can specify a particular API version...
All of the card readers are the BBPOS WisePOS model
If that matters
So this all happened because I wanted to upgrade my SDK version, and I checked my logs and noticed that I have requests everyday that use an outdated version
If I can't change the stripe-terminal-android version, does that hurt me at all? It seems like it's been fine to this point
viscid mist
It likely doesn't hurt, unless you're trying to adopt a feature that is only available on a new version.
Can you confirm if this flow is the one you're using in your process?
https://docs.stripe.com/terminal/payments/setup-integration?terminal-sdk-platform=android
If so, I think this may be related to the API version being used when creating the Connection Tokens (which would mean I was mistaken before when I said this isn't relevant to your server setup 😅 )
Or are you using the Server-driven flow that we describe in that doc?
long ferry
Server driven
oh weird. I commented out the stripe_version in the StripeClient for all these
that explains it!
I can't remember why I did that...
viscid mist
Ah ha! Nice spot! I'm happy to keep looking if uncommenting that doesn't do the trick.
long ferry
No that should do it. But that brings me to the original reason why I was updating the SDK in the first place
I am trying to retireve a connected account
And the response I get is very different than what the docs say I should get
So I updated the SDK to the most recent version
(which made me check the API version for requests, which led to my initial post)
But now I need to figure out why I can't properly retrieve a connected account
$account = $stripe->accounts->retrieve($record->stripe_act, []);
This is what I get when I try to retrieve a connected account
And the docs say I should have access to a lot more fields
Specifically, I need the created timestamp
viscid mist
Can you copy/paste that Account ID here?
long ferry
acct_1IcySiBSy15MDUjf
viscid mist
I have an idea of what is going on there and am working on running a test. I think instead of passing the Account ID like that you'd pass it via the stripe-account header:
https://docs.stripe.com/api/connected-accounts
Hm, maybe not. Admittedly I'm running a Node test since that was closer than a PHP one for me, but I'm seeing the account returned as expected, even when specifying our newest version.
Which version of stripe-php are you using?
long ferry
I just updated to the latest version
But it was the same in the older version I was using
long ferry
Which version of `stripe-php` are you using?
16.2
long ferry
I have an idea of what is going on there and am working on running a test. I thi...
I tried passing it as an option like you normally do for connected accounts, but that returned an error
In that case I used my main account as the account ID
$stripe->accounts->retrieve('main_account_id', [], [
'stripe_account' => $record->stripe_act,
]);
Hm, I'm not seeing anything change in the output when I change API versions. Can you share the full code you're using?
I'm running this:
"stripe_version" => "2024-10-28.acacia"]);
print('Stripe initialized ');
$account = $stripe->accounts->retrieve('acct_1PldFZPNNiJhwtaF', []);
print($account)```
and seem to be seeing the full account object printed.hmm
$stripe = new \Stripe\StripeClient([
'api_key' => config('services.stripe.sk'),
"stripe_version" => '2024-10-28.acacia',
]);
$account = $stripe->accounts->retrieve($record->stripe_act, []);
dd($account);
I still get the same thing even when I hardcode the version number
winged crater
Hello! I'm taking over and catching up...
long ferry
Hello!
winged crater
Is your dd() function producing that output?
long ferry
yes
I just deleted my vendor folder and reinstalled all vendor files, including Stripe
same thing
winged crater
Instead of using dd() can you try something like echo $account;?
I'm wondering if dd() is doing something.
winged crater
🤔
long ferry
For what it's worth, I only need the created timestamp of the account. But I don't know any other way to get that other than retrieve
So I'm not missing something obvious?
winged crater
Not that I'm seeing, no. Investigating now...
long ferry
Oh. Maybe this is relevent. I need the created timestamp because I need to establish manual payouts for accounts created before 2023-10-23 because I need to customize the statement description on the bank account
I chatted with someone earlier (https://discord.com/channels/841573134531821608/1306253200923430993)
Who said that accounts created before that date have an issue and they need to be upgraded
This account was definitely created before then
Could that be why it's not returning the correct information?
He said that would only affect the ability to customize the payout description though...
winged crater
Yeah, I don't know why the created propery is missing. I've never seen anything like this before. Will be a few while I investigate/research.
long ferry
Thank you! Or if there is a different way to get the created property of a connected account (its actual creation date, not the date it was linked to my account)
winged crater
Okay, I found out what's going on. Unfortunately you won't be able to get the created timestamp for these accounts. For connected accounts, we only provide the timestamp for when the account was connected to your platform under created. Further, for certain types of accounts, like Standard accounts where you're not the controlling platform, we don't provide created at all.
long ferry
I'm confused... why does the documentation say differently?
winged crater
It's an oversight. I'm going to flag that internally so it gets fixed.
Let me read your earlier thread to get context on the main issue you're trying to solve...
Okay, caught up. Looks like your best bet is to wait for support to get back to you about making the change discussed in the previous thread. I can't think of any other approach or workaround in the meantime.
long ferry
I guess I just have to convert all accounts over to custom payouts through the API
Which I was hoping to avoid because with automatic payouts you can see what they are comprised of
winged crater
Why are you not able to wait for the change to your accounts?
long ferry
I have a deadline. My client needs to see the change quickly
I can switch it back later
I was just trying to avoid doing that