Here is a side by side figure of Chrome and Brave of the same order form page: (Chrome on the left, Brave on the right): Basically the remote payment form wasn't showing up. When visiting one of the payment pages in my store with Brave, I noticed that the payment page wasn't working. Brave also provides built-in ad-blocking by default so overall the browsing experience out of box is much better than you get in stock Google Chrome, because a lot of the crap ad content that makes up a good part of the Web these days is not being loaded. Brave is a Chromium based browser that provides most of the features of Chrome without Google tracking you each step of your browsing adventures. Nice.īut - and there's always a but - today I noticed a fairly major problem: For the last few months I've been using the Brave Browser for most of my Web browsing.
Order processing is very quick through this remote interface and with BrainTree at least as a bonus you can process PayPal requests just as you do Credit Cards using the exact same process with a different 'card type' - no need to use a separate PayPal order flow. Or, if something does go wrong the responsibility lies with the processor since they are the ones handling the Credit Card transaction data. The SDK and the remote hosted form keeps the credit card data on BrainTree's server which reduces the risk of credit cards getting hacked during the payment process. These days it's a pretty common scenario to use a JavaScript SDK that essentially removes the payment detail handling on the server so that the server never actually touches the credit card data. Braintree has both server side and client side SDKs and the site uses the JavaScript SDK to remotely render the partial payment form into the overall order form. On my site I use a custom Web Store and the payment integration is going through BrainTree's CC Processing APIs. I just ran into an interesting issue with my Web Store.
0 kommentar(er)
