#farias_best-practices

1 messages · Page 1 of 1 (latest)

fathom jackalBOT
#

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

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

#

We wish we could help, but you need to talk to Stripe support

We can only help on Discord if all of the following are true:

  • 🧑‍💻 You must be a developer
  • 🛠️ Your question must be about building a Stripe integration
  • ⚙️ Your question must be technical/developer focused
  • ⏱️ You must be available to respond in realtime
  • 👥 You must be comfortable receiving help in public (this is a public server)

If any of those aren't true please contact Stripe support.

If all of those are true we may have misunderstood your question; please provide more details below.

Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.

copper valve
#

We can only help with developer questions in English here, for help in other languages please contact support as above.

manic patrol
#

Sorry, i can send the question in English

#

I'm building a Saas (very short deadline, that's why I came to support) and i need a membership recurrency

By what I saw at the doc, the easier path is by payment links and then customer portal, but my service has a Sign-up endpoint, so how can I integrate this?

copper valve
#

my service has a Sign-up endpoint
What does this mean?

manic patrol
#

create account

copper valve
#

Payment Links are re-usable URLs you can direct customer to in order to pay you / sign up for subscriptions etc

#

If you want to tie payments to specific account, you can either use Checkout Sessions, or with payment links if every customer pays the same amount you can append your account ID as a client_reference_id query parameter, then associate those payments to accounts during fulfillment handling

manic patrol
#

Understood, I will be trying with this approach