#pingpong2_api

1 messages ¡ Page 1 of 1 (latest)

turbid pantherBOT
#

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

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

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.

jagged jolt
#

hello! I don't think there's any way to remove this message at the moment, but you make a very good point and I'll suggest that if you would like to see this change, write in to https://support.stripe.com/contact/email to explain this request as that helps the product team capture demand for prioritisation

narrow hull
#

so there isn't any way to remove wordings like 1-2 business days and microdeposit even tho skip is enabled(no verification needed)?

jagged jolt
#

yeah, there's no way right now

narrow hull
#

ok so regardless of having skip enabled or not, we must show 1-2 business days part or micro deposit wording correct?

#

or if we build custom input fields then we wouldn't see it right?

jagged jolt
#

ok so regardless of having skip enabled or not, we must show 1-2 business days part or micro deposit wording correct?

yes the Stripe UI will show 1 - 2 business days and/or the relevant microdeposit wording

if we build custom input fields then we wouldn't see it right

This would possibly only work for microdeposits

narrow hull
#

what's the par that wouldn't work?

#

part*