stormy

So if your customer is a company, they can't own the domain. How does Blesta solve this? To this problem, add this one: the domain Registrant can't be changed or modified without a domain transfer.

Yes, that doesn't work anymore, or it shouldn't. If it does, it creates wrong contacts that can be cause for termination of the domain. I manage a few thousand .es domains through a LB registrar, my company is established in Spain and while not accredited myself, I helped a registrar get accredited a few years back. If you want me to help, I'm happy to. Anyway, I'm don't want to hijack the thread. Contact me privately if you need me.

Yes, the documentation is not clear about this. We've had to work closely with LB for quite some time to solve this conundrum. Here's the key: The Registrant Contact of a .ES domain name may either be a natural person/individual or a company. However, the Admin, Technical and Billing Contacts must be natural persons/individuals only. -If the Registrant is a person, then the Registrant and the Contact are the same and they have the same es_form_juridica, es_tipo_identificacion and es_identificacion -If the Registrant is a Company, then it gets more complicated, because the Company can't be a contact, the contact needs to be a person. So you have to supply two sets of fields, one for the Registrant (Company) and one for the domain Contact (person). Am I making sense?

Almost, but not there yet. We need to ask for 5 additional domain fields: 1. Registrant type 2. Registrant document type 3. Registrant document number 4. Domain contact document type 5. Domain contact document number This is needed for domain transfers too, something WHMCS hasn't been able to fix. We have a third party module because of this.

Laundry list: -I'm in Spain, so I need a payment module for Sermepa, used by 100% of the Spanish banks. That one should be easy to do. -I would need to test the LogicBoxes module thoroughly, especially for .es domains, that have some extra requirements/quirks. It took us years (literally) to solve this in WHMCS. -I also need a module for Spanish registrar Virtualname. Those are the basics. Then there's the 10-12 modules we had to add to WHMCS just to get it working properly and issuing invoices that are legal in the EU, etc. Nothing fancy. We just sell domains and three different hosting plans, and have a few thousand customers. If you guys are for it, I would love to privately send you a (very) long list of everything we had to do to our WHMCS, with the explanations behind it.

Here's another vote. I think I will be buying Blesta even if it doesn't have all the modules I need right now, just to play with it and try to get it ready as soon as possible for my WHMCS migration.