cpt.mactavish

[devout oracle]

Good questions, looking in to this and will get back to you

[south kestrel]

Sure. Take your time 🙂

[devout oracle]

Our API reference does show that it is possible to set metadata on the payment links, I am unsure if this would be copied to the resulting checkout session, I am. trying to check if you can see what link created a specific checkout session which would help retrieve the metadata even if we don't copy it over. https://docs.stripe.com/api/payment_links/payment_links/object#payment_link_object-metadata

After reading your description a few times, I am still not fully clear on what an application is in your context. Are you selling access to various applications or something?
And when you say a separate account, I assume you mean a separate Connect account for each application, or something else?

[south kestrel]

an application is basically a web app.
Right now we have multiple apps (app1, app2, app3) which use same stripe account.

I am not very sure of the terminology regarding accounts but as highlighted in screenshot, that's what I am considering as account.

To give background on the situation,
When we were starting off, we considered creating separate accounts for each application.
At that time, each account was approved separately by going through documents stuff. Now stripe has changed it and it doesn't ask for documents and business verification for newly added accounts.

[devout oracle]

Gotcha, it is honestly up to you whether you want to use one account or multiple here. Assuming you aren't doing this for regulatory reasons or to have accounts for different regions, having separate accounts would mostly be an organizational difference. By using separate accounts, you are keeping the data more separated, as these accounts can't list payments, products, etc from each other.

The main downside would be that it may be a bit more complicated to manage multiple sets of API keys but that wouldn't be much more complicated

[south kestrel]

Thank you. I had assumed the similar. I looked into the Pricing table docs and it seems that in a worst case scenario, the client-reference-id can be used as application identifier. If metadata is supported, it would be great. Although I haven't found anything in docs that shows how to send metadata.
Maybe something like might be supported or can be done in future.

<stripe-pricing-table
    pricing-table-id='{{PRICING_TABLE_ID}}'
    publishable-key="pk_test_"
    metadata="{{JSON_ENCODED_METADATA}}"
>
</stripe-pricing-table>

[hardy glacier]

Hello! I'm taking over and catching up...

If you have separate apps we expect you to use separate Stripe accounts: https://docs.stripe.com/payments/account/multiple-accounts

You must use separate Stripe accounts for projects, websites, or businesses that operate independently from one another.

[south kestrel]

can you please confirm if it's possible to send metadata with checkout sessions initiated via Pricing table?

[hardy glacier]

As far as I know it is not possible.

Sorry, I missed that question.

What's your use case?

[south kestrel]

Would you like me to rephrase or just copy paste my long message here again?

[hardy glacier]

No, sorry, I mean what's your use case for the metadata specifically? Is it just to identify which website is being used?

[south kestrel]

Yes. This is primary and for now. Any other cases that come up in future can be handled via it.

[hardy glacier]

No, you should use separate Stripe accounts instead.

[south kestrel]

Thank you guys.
I really appreciate your help & insights

[hardy glacier]

Happy to help!

[south kestrel]

an unrelated question.

Is it possible to have this chat exported in a user presentable format for sharing? something like chat transcripts over email.