#hillct-checkout-customdomain
signal gale
Hi 👋
We can't really tag a ticket
turbid light
Tha's unforunate
Can you review my thread here from Friday and suggest an approach that might promp mor meaningful responses from them?
signal gale
There are too many people asking for help to dig into old threads. Can you summarize your question?
turbid light
I's very short, but essentially, I'm not able to setup the custom subdomain billing.christian.com because when I enter in the dashboard it throws an error saying it's claimed by another stripe merchant. his is in fact a possibility because we bough h domain on he secondary market in 2018, but he stripe dashboard throws this error and does not provide the relevant DNS TX record values that would allow us to prove our current ownership. SO far our ticket has yielded responses hat instruct us to follow the dashboard procedure that yields the error, prompting ticket submission.
Essentially, all we need to know are he DNS record values to be set, to prove our ownership of he domain and subdomain but the existing dashboard interface has a workflow that causes them not to be provided in the automated fashion
signal gale
Unfortunately this isn't something I can help with much here. The only guidance I can provide is what we show here: https://stripe.com/docs/payments/checkout/custom-domains
turbid light
What needs to happen here is w need the DNS values you require us o s to demonstrate our legitimate ownership of the domain, but the dashboard UI sops here instead of providing the normal modal window with DNS TXT values to be set
signal gale
Unfortunately I cannot help with Dashboard related issues. I can only offer help with integrating with the APIs directly
turbid light
OK, are there API methods I might use to request the relevant DNS values one might use to automate setup of multiple accounts?
soft valeBOT
signal gale
Not that I know of
turbid light
OK, well apparently we won't be using the checkout service on our own domain and won't be paying the $10/month related to it, specifically because nobody at Stripe was able o resolve a simple namespace ownership collision. Thanks.
crystal shuttle
@turbid light that's definitely your choice in that case. We unfortunately can't help with account specific issues here. You emailed on a Friday, it's Monday, you could also wait a few days to get a definitive answer
hillct-checkout-customdomain
turbid light
@crystal shuttle Normally, I would agree as to waiting a few days except I've already received three responses to the ticket each of which sadly demonstrated that the respondants hasn't even read the content of the ticket
crystal shuttle
Sure but you also responded and your ticket is still open and someone will look into it. It's not common that someone tries to register a domain that is already used by another account they don't own and aren't aware of when they bought the domain. We will find a solution, but you have to be a bit patient as they look into it
turbid light
we bought the domain in 2018
we can provide whatever paperwork is required. We just need you to provide a process for us to submit i to you
There's even a secure documentation request mechanism on your website, and TOS states that you might seek verification of domain ownership. All of that is fine. Just initiate the process!
crystal shuttle
Sure which you are working on with our support team, not me
turbid light
The problem is I haven't gotten any meaningful responses from the support team, nor have hey indicted any dowubt hat w own the domain
you're the first to question that
crystal shuttle
All good! Someone will investigate further and help you find a viable resolution. But again this is not the place to escalate account specific questions as we can't help with this here
turbid light
OK, I've found an alternate route. I'll go through he email domain process. Will ha maybe speed things along? in that it will actually provide me DNS TXT records through which I can actually demonstrate domain ownership?
Im going to setup he email domain verification DNS values and if that doesn't get this dome, We're going to move to a payment processor that can handle these trivial issues efficiently. I've stood by Stripe for 13 years, but enough is enough.