#crawl_api

1 messages · Page 1 of 1 (latest)

left quiverBOT
#

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

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

somber echoBOT
steel carbon
#

Hi there 👋 it's not GA'ed yet, but we're working on building something that I think sounds like a perfect fit for that scenario, known as Sandboxes:
https://docs.stripe.com/sandboxes

I'd suggest taking a read through that doc. If it sounds like what you're looking, I'd suggest signing up Stripe Insiders as mentioned near the top of the page, and indicate you're interested in trying this out.

orchid belfry
#

Also, in the meantime
What's the recommendation from the stripe team ?
What's the best way to mitigate this ?
Keep our reconciliation or do something better than this ?

#

Right we are workbench power users too, this has been a game changer for us

steel carbon
#

Not that I'm aware of, we aren't familiar with the beta flows in this forum, so I don't know if that can be expedited.

Either keep splitting things like you're doing, or spin up another Stripe account. The latter comes with the overhead of making sure all the settings between the accounts stay in alignment.

orchid belfry
#

okok sounds good
last q
any estimations date for the sandbox release ?

#

(official)

steel carbon
#

Sorry, I don't have insight into that either.

orchid belfry
#

thanks 🙏

left quiverBOT