#wolverineviv_api

1 messages ¡ Page 1 of 1 (latest)

pearl prismBOT
#

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

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

turbid shale
#

Hm can you explain the product structure a bit more? How does setting metadata on the Connect accounts help with you differentiating product objects?

chilly citrus
#

We have one web product and a different desktop product. Both are considered different revenue streams and we need to track how many people are using it, how much volume of payments is flowing in each product ecosystem. We have one platform account for Stripe.
Through Stripe support they mentioned we can use metadata to store something like
product: web or product: desktop that will be a paremeter we can use to filter for reports to differentiate between the two

#

but when we ran into the error, they informed us to ask in discord channel

turbid shale
#

In the above request you shared, you're attempting to set metadata on the account object

#

I'm not sure how that helps

#

Is there a reason you're doing that

pearl prismBOT
chilly citrus
#

let's consider an example where through web 10 users sign up for stripe. Through desktop 5 users sign up for stripe.
Now I have total 15 connected accounts in Stripe all of which I see in a single place.
If I'm able to store the metadata, then I'll be able to differentiate betweeen which account belongs to Desktop or which account belongs to Web

#

If you think this is not the right way to store this information, I'm open and request for suggestion on how to achieve this where I can filter reports and filter connected accounts based on the product in the same platform account.

pearl hemlock
#

Hi, taking over as my teammate needs to step away. Let me catch up.

chilly citrus
#

Initially we integrated account links for our entire integration. But then stripe accelerate team who connected with us told us to instead start using OAUTH so we completely switched over

pearl hemlock
#

Do you know what the reasoning was?

chilly citrus
#

It was last year so I might have forgotten the full concept. I think the reasoning was, we would onboard business who might already have a stripe account that they want to connect with us and some business customers who never used stripe and signing up first time. We wanted a seamless onboarding expereince for both of them to work in the same manner. I guess OAUTH was the only option?

pearl hemlock
#

Ah, yeah

#

In that case, you can't make updates like you shared above so there are trades in there

chilly citrus
#

it makes sense that we should not make any changes or updates to the customers business stripe account. But what I'm unclear is why am I not able to set metadata for my connected account

#

metadata will have no impact for the customer's actual account. it'll only be for our platform use

pearl hemlock
#

I assume you make Direct Charges using the Stripe Account Header, you can pass the metadata that way and keep track that way

chilly citrus
#

thank you. Will explore that as an option

#

Does Stripe Dashboard Reports have a way in which I can give filter based on this metadata so that it can display the total volume and other reports based on my metadata object?

#

let's say I store metadata product: WEB or product: DESKTOP

#

Can I filter based on this in the reports page?

pearl hemlock
#

On this channel we do not know a ton about the Dashboard/ reporting as we're mainly focused on the API. You can definiltely try in Sandbox

Hope you enjoyed Sessions!

chilly citrus
#

thank you. Yes sessions was good

#

For a use case like ours, is the primary suggestion from Stripe is to create one organization and 2 platform accounts? Is there a way I can have a single api key/secret at the organization level?

pearl hemlock
#

If these are two separate entities, or two separate functions sure. However, if is is just two different product offerings then no.

chilly citrus
#

these are just 2 different product offerings but the same business entity owns both of them

pearl hemlock
#

In that case, if I were you, would keep them under one account

chilly citrus
#

thank you.