Cryptography is a quite academic field. Outside of universities, practice of cryptography tends to be "applied crypto", which feeds on academic papers while contributing its own perspective on things, in particular with regards to implementation issues. In any case, this means that whatever you do in cryptography will involve reading a lot of research papers, and, correspondingly, the formal degrees about it are academic. If you want to go that road and be recognized as a "cryptographer" through certifications and degrees, then go get a PhD or at the very least a Master's degree in cryptography.
There are alternate roads to building your crypto street cred:
You might demonstrate your deep knowledge of the field by flooding some well-known public forums or Q&A sites (e.g. this very site, crypto.stackexchange.com) with hundreds of well-researched and explained answers that make people instinctively think of you as "that guy knows his stuff".
While paper publication in peer-reviewed conferences or journals is a difficult art, "publishing" software implementations is simple; you just have to create a free GitHub account, and roll with it. If you manage to write some kick-ass piece of crypto software, that people find useful and appears to be of high coding quality, then you could also gain some reasonable level of recognition.
There occasionally are some "cryptographic competitions" (some are referenced here; an ongoing one is the NIST call for Post-Quantum algorithms) in which anybody can submit a "candidate". This is substantial work, and little glory is achieved if it gets broken right away. But if a candidate survives one or two rounds, then it can lend some credibility to the authors.
The common theme in all of these is that you should show, at all times, that you understand the academic side of things, and you know not to make unsubstantiated outrageous claims of security.