I've seen web frontends that encrypt submitted credit card info with a public key, then had billing backends that re-encrypted with a symmetric key (usually in a HSM).

That was strictly for performance overhead and key rotation flexibility. Perhaps name.com didn't care about that.