#cberube_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1227994635930959935
đ 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.
- cberube_unexpected, 5 days ago, 41 messages
- cberube_error, 6 days ago, 63 messages
You need javascript to accept stripe payments on the web
I know that. So, what is the proposed resolution path for unsupported devices.
Use a supported device
Javascript is a requirement
If you're using a device that doesn't support it/have it, you can't use that device
Either that or handle pci compliance yourself entirely and pass the raw card details to us
But that requires extensive work on your end and for your account to get approved to do that
Is there any issues if a customer sends he's credit card number throught an SSL secure form, for instance.
So, we can resort to phone instead of passing any credit card information.
What do you mean
Sending an email so that customer support handles the buy process through the dasboard.