Most host these days offer web hosting plus the option to register a domain name on behalf of the web hosting company.

Now when a host registers a domain at say Network Solutions or 000domains do they use the customer's credit card number or their own one?

And if indeed they do use the customer's credit card number to register a domain for the customer isn't that illegal?

Also if the host uses their company credit card to register a domain then wouldn't the customer be able to get that number once they log in their domain management interface?

Any info is appreciated.

thx

As long you use it to register their own domain, I think it's OK. To make sure, you'd better contact netsol or 000domains.

Hi,
I like to use ukreg.com, they allow me to register domains for clients. They get the domain in there name but I get control over the domain, DNS etc, if a client wants the access them self, they just set-up an account for free and I can transfer the admin of the domain over to them. Its very good, I use it all the time.

We just register our clients domain with our cc but the client owns the domain.

From what I've heard it isn't legal for you to enter their credit card info in for them. I'd charge them and then use your CC to register the domain separately.

i'd have to side with justin on that :)

This is a very good question that i'm sure has been on the mind of many resellers.

If I register the domain for the client with my cc# .. that is perfectly legal. But, when the client logs into his domain management account, he can see my CC#. I don't want that to happen.

Anyway around this?

If I am offering a "free domain" with a full year of web hosting paid annually. I am offering the deal, I should be the one to register the domain, and not push the client to register themselves.

Any feedback is welcome.

You can see the billing contact information, but not the actual credit card number. At least that's how it is with 000domains.com.

You could also log in after you're done registering the account and change whatever info you want to.

I say charge their CC and then pay for the domain with your own CC.

You should not be able to see any of the CC information, if they slow any of it, it will be the last 4 digits.
I'm sure they would not show the CC information for security reasons :)

Easy way to deal with that is don't go with a place that stores your CC info like that OR remove that information after the domain is registered.

Why not just become an affiliate at http://registrars.com

They bill you monthly for the Domain Names you register. They only charge you $19.00 per Domain Name and you can increase the price to what the market will handle.

Ummm that price is a bit high. It isn't super high, but saving the client a few bucks is always a plus and you can get domains for half as much elsewhere.

Did you ever think about this;

if you use your credit card for the domain,,, then you charge the customers credit card...

Ok.. Now, what if that was a stolen credit card....
Two months later you get a charge back.
Now, you paid for the domain, it is in the customers name, and you are screwed...

use the customers credit card when ever it is an option. It will save you the hassle. If they charge back to the registry, the registry will kill the domain. If they charge back to you, the customer keeps the domain, and you get the shaft.

Work Smart...

Tim L :cool:

I guess it's a risk you have to take. Anyone know how the BIG guys do it.. e.g. burlee, webhosting.com, etc?

THERE is a RISK if you use THEIR credit card. For example, if they submitted a stolen credit card number and you use that to register a domain name, your BUSTED..

Because you used a stolen card the registar will think your a theif and send your information to the cops who will track your IP address and investigate you. Meanwhile your just a web host trying to register on behalf of a bad client. :bawling:

????

You cannot use your customer's credit card at another site and register a domain for them, so it really isn't an issue. This is illegal.

I'd take a look at:

http://www.itsyourdomain.com
http://www.domainbank.com

as these two will bill your customer's card, for you and send you the difference (they make, verses what 'you' charged your customer for the domain - you can set this).

You shouldn't use your own cc either.
Some company's (e.g. register.com) will automatically renew close to expiring and bill you.
Defiantly use a domain reseller program or implement a 3rd parties software into your signup process.

Here is an example of register.com programs.
http://www.register.com/partner-affiliate/index.cgi
Some cheaper registrars have similar programs.

As far as using another persons cc not only being illegal, just imagine if it was stolen and here you are ordering domains with it.

OK - so if the consensus is that it is illegal for you to enter your client's CC card - then essentially you are acting as a reseller of the domain name. This is interesting, because I've been searching through these boards looking at discussions about reselling domain names and have been looking over the web sites of some of the registrars that offer reseller arrangements - co-branded and API.

The first question of course - with cc fraud being what it is - is what happens if there is a chargeback or somthing where the domain name has been issued but the bank reverses the cc charge. It seems to me that the standard policy is that the money comes off your account with the registrar (off what they owe you in billings) and you end up owning the domain name. Interesting - it seems that no matter which way you go - you end up taking the risk.

BTW, the sites I have checked out so far are:

godaddy.com
stargate.com
gkg.net
registrars.com
registerengine.com
dotster.com

I'm just looking around at the moment.

Yep, the risk of being a middle man is that you get to deal with the bogus charges. If you just do a referral thing where you have the client enter their info to the registration place and register it themselves, they do a chargeback, you just don't get the referral/affiliate money for that domain.