Customer Paid for a Domain. Is Payment-to-Registration Time a Real Metric?

[NiceNIC]

Hosting companies usually watch payment success and provisioning time.

Domain orders add another checkpoint: the registration itself.

If a crypto payment needs confirmation before the registrar call is made, a domain can remain available even though the customer has already started paying.

For a routine order it may not matter. For a strong name, it can.

Should payment-to-registration time be treated as a real provisioning metric?

 

[SenseiSteve]

I’d definitely consider payment-to-registration time a real provisioning metric, especially for domains.

With hosting, a few extra minutes between payment and provisioning usually isn’t critical. With a domain, the product can literally disappear during that window. Until the registrar successfully completes the registration, the customer doesn’t actually have the domain secured.

Crypto makes this more noticeable because confirmation requirements can introduce additional delay, but the same principle applies to any payment method that holds an order before registration.

I think the important metric is not simply “payment received,” but time from the customer committing to the order to successful registration at the registrar. If providers tracked that separately, it could expose delays that normal provisioning statistics never show.

For an average domain, a few minutes probably won’t matter. For a short, valuable, or highly desirable name, those few minutes could be the difference between registering it and explaining to the customer why someone else got it.

 

[Mivocloud]

Good question, I would say that until the payment is received, you are not obligated to buy a domain name. For example, a customer asks for a specific name, which makes the payment, but while the payment is being received, someone else has bought the given name. Well, there's nothing we can do about it because the payment hasn't been received yet and we can just offer another domain name.

 

[NiceNIC]

I’d definitely consider payment-to-registration time a real provisioning metric, especially for domains.

With hosting, a few extra minutes between payment and provisioning usually isn’t critical. With a domain, the product can literally disappear during that window. Until the registrar successfully completes the registration, the customer doesn’t actually have the domain secured.

Crypto makes this more noticeable because confirmation requirements can introduce additional delay, but the same principle applies to any payment method that holds an order before registration.

I think the important metric is not simply “payment received,” but time from the customer committing to the order to successful registration at the registrar. If providers tracked that separately, it could expose delays that normal provisioning statistics never show.

For an average domain, a few minutes probably won’t matter. For a short, valuable, or highly desirable name, those few minutes could be the difference between registering it and explaining to the customer why someone else got it.

Thanks, Steve. I think that’s a really good way to look at it. I’d probably split the timing into two parts though, payment confirmation, then registration, just so you can see where the delay actually was.

Good question, I would say that until the payment is received, you are not obligated to buy a domain name. For example, a customer asks for a specific name, which makes the payment, but while the payment is being received, someone else has bought the given name. Well, there's nothing we can do about it because the payment hasn't been received yet and we can just offer another domain name.

Thanks, Anatolie. That’s fair from the provider side....