How recently was this? I used the CSE encryption library instead of transparent redirect in my implementation, and it wasn't bad at all.
I'm actually a bit confused by this announcement, as it looks essentially the same as their existing client side encryption solution that they've had for at least a year?
I explain this in a comment that's a bit further down the page but here it is in a nutshell:
* You're right that this is very similar to our previous offering. At its core, the encryption logic is the same.
* While both libraries offer an object which will encrypt your data, that's literally all our previous offering did. New helpers used in conjunction with data attributes eliminate the need to write custom onSubmit handlers, making your integration far simpler.
* We host the JavaScript, making linking directly to it an option.
These things make our JavaScript library substantially easier to use. That, plus the fact that we now recommend Braintree.js over Transparent Redirect motivated us to rebrand it.
I'm actually a bit confused by this announcement, as it looks essentially the same as their existing client side encryption solution that they've had for at least a year?