#dbugger_code

1 messages ¡ Page 1 of 1 (latest)

willow mistBOT
royal masonBOT
#

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.

willow mistBOT
#

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

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

rigid halo
#

Hello, it is not possible to use the Payment Links API without using our Prices API. Some of our API's do support one-off price definitions but those do still create a one time Price object, albeit one that doesn't show up in the dashboard or API list call

sinful schooner
#

But will they create a product in the Product catalogue?

#

?

rigid halo
#

Yes, all of our APIs require at least a product to be defined at minimum

sinful schooner
#

Is there a way to create a payment link, without creating a product?

rigid halo
#

Unfortunately not

sinful schooner
#

...which means there is no way out of polluting his product catalogue of thousands of useless repetitive entries?

rigid halo
#

If they are unique things that you are selling then yes. If you want to file some feedback about it, our support team can do that for you https://support.stripe.com/?contact=true

sinful schooner
#

I am not selling them. This is the customer using my Platform through Stripe Connect

#

But he will be managing prices and products through my platform

#

as my own service, meaning I do not want to consolidate Stripe product catalogue with mine

rigid halo
#

I guess a more accurrate statement would have been "If they are unique things being sold via Payment Links on your account then creating a new Product for each will be required"

#

I understand that that is not ideal for your use-case but that is what the current state of where our Payment Link and Products APIs are now

sinful schooner
#

The only solution that would come to mind is consolidating the Product catalogue in my backend with the one in Stripe but that... a colossal task

#

Not to mention that there is no guarantee that my users will want to connect their Stripe account to my service

rigid halo
#

Unfortunately I am not sure of a better solution here if you are using a connect structure where the links are being created on your account. The links would need to live on your platform and therefore the products as well. Unfortunately no workarounds here at the moment

sinful schooner
#

The links are being created on the user's accounts, not the platform's account

rigid halo
#

Then there isn't a way to avoid their accounts having many products