#aye-account-dotnet
worthy thorn
When you say you're not able to get it, do you mean it's not showing up in the payload?
crimson iron
taking over as this thread is busy
(which you asked me to do @worthy thorn and I removed you :p)
@candid sphinx our stripe-dotnet library will mirror all the details you see in our public API reference at https://stripe.com/docs/api/accounts/object
desert solarBOT
crimson iron
So if you look at the docs you see https://stripe.com/docs/api/accounts/object#account_object-company-structure
And that maps to this property https://github.com/stripe/stripe-dotnet/blob/master/src/Stripe.net/Entities/Accounts/AccountCompany.cs#L111-L112 in our stripe-dotnet library in the AccountCompany class which maps to the Company property on the Account class
candid sphinx
so in my assembly browser AccountCompany doesnt contain the structure field. I was wondering if this was introduced in a later version
I was wondering if there was a way to retrieve this field some other way in this version, without doing a full upgrade
crimson iron
Which version of stripe-dotnet are you using exactly? This is multiple years old so it depends how behind you are
candid sphinx
using v34.0.0
crimson iron
https://github.com/stripe/stripe-dotnet/blob/master/CHANGELOG.md#3400---2019-12-03 that's from 2019 so it's quite old
Unfortunately there's no alternative. We have a newer feature documented here https://github.com/stripe/stripe-dotnet#properties to access newer properties in older versions but it was added back in version https://github.com/stripe/stripe-dotnet/blob/master/CHANGELOG.md#35110---2020-03-30 which is after yours
So I think for now your best approach will be to invest into upgrading
candid sphinx
ok sounds good that for the help, will look more into it. From the looks of this, structure was added into v34 in the following version: https://github.com/stripe/stripe-dotnet/blob/master/CHANGELOG.md#34180---2020-01-30
So it might be worth upgrading, as long as there is not too many breaking changes
crimson iron
we use Semantic Versioning. As long as you say under the same major version there's no breaking change
candid sphinx
ok great, thanks for the help