And what happens when Braintree (owned by Paypal) decides to drop you as a merchant? What if you're running a website supporting Tor, or selling proxies or VPNs, and they decide your content is "against policy?"<p>They'll "drop" you, and suddenly your "drop in" SDK is completely worthless and you're forced to write your billing system from the ground up.<p>From a risk perspective, using a solution like Chargebee, that integrates with multiple merchant accounts (including Braintree), is a much better choice. If for whatever reason your merchant drops you (it does happen!), you don't need to make any code changes. You only need to swap out the backend merchant account in your Chargee dashboard.<p>These "batteries included" payment solutions are nice for getting up and running quickly, but if you have any semblance of long term planning, it's a bad idea to build your entire billing infrastructure around the API of a single merchant account provider.
Some usability things I noticed on the Drop-in UI Sample Page: (<a href="https://www.braintreepayments.com/features/drop-in" rel="nofollow">https://www.braintreepayments.com/features/drop-in</a>)<p>It appears that the PayPal is a header, rather than a button, it has no call to action. Separating the credit card form from the button and giving it a clear header (Like: "Pay With Credit Card") would help indicate the choice of PayPal or Credit Card.<p>Also, I'm not sure if it's intentional, but the credit card form doesn't actually do anything. Completing the form with a test credit card gives no follow-up call to action. This could be confusing to people wanting to see a "working" integration.
I don't quite understand the recent developments at Braintree. We were using both them and PayPal for awhile before deciding to turn out card transactions over to PayPal also as it would secure a better rate. Meanwhile BrainTree has been working to make it easier to split processing between the two. Is the end goal here to make sure you're paying the highest rate? Why wouldn't you only use PayPal?
Will this be able to save credit cards on the device so the user doesn't need to re-enter their credit card every single time they need to make a purchase?
Huh. I'm confused, what's to stop someone from copying the "Paypal" button and associated modal, but simply directing the form to themselves to absorb the Paypal credentials?<p>I suppose anyone could do this to take advantage of silly users, but this is encouraging users to trust 3rd party websites by design.<p>Seems wide open for phishing.