Another month, another set of updates! Like last month, we’ve spent some more times on our payment forms and Captcha, in particular giving our customers the option of requiring login to proceed with making a payment.
Generally speaking we recommend allowing anyone to make a payment, even if they’re not logged in. In fact, this capability is one of our founding principals: that people should be able to interact with your business without first having to sign up for an account.
There are however a handful of circumstances you might want to require people to log in. One area we’ve been focusing on lately is bot prevention, and as we mentioned last month we’ve added captcha to all our payment forms for logged out users. While it’s rare, bots can still at times get past Captcha prevention. In the unlikely event a bot successfully starts spamming your payment forms even with Captcha in place, now you have another line of defense and can put up a “log in wall”.
Additionally, our customers in the European Union are now subject to Secondary Customer Authentication requirements, and these secondary authentications usually expire in 1 hour. So if a logged out user makes a payment in Europe, there’s a good chance it’ll fail if it’s not matched within an hour. For these studios, depending on how quickly you’re able to match payments, it might make sense to require people sign in before making a payment as those are processed immediately.
In addition to the login options, we’ve also updated the language around your captcha selection options to indicate that you’re choosing between using v2 captcha and v3 captcha, made some nice updates to the website widgets page to more prominently display your mobile app site url, and shipped a number of other small bug fixes and system updates.
More updates to follow next month!