Brex CTO here. I completely agree with you, the issue isn't that we expect something in return. When you invest in a new language community, it's not about expecting something in return, you're investing in its growth. We've sponsored several core language projects and maintainers, and have open sourced many libraries, and we did it so that the ecosystem gets more fuel to develop and grow.
But that also doesn't mean we never evaluate what makes most sense for us as we continue growing ourselves. We have >400 engineers at Brex, so many things internally have had to evolve over the years, including our decision to build things in different languages (we now additionally support Go, Kotlin, Python & TypeScript, each for specific domains).
Even as we write more backend services in Kotlin, Elixir will continue existing for a long time, and we're continuing to work close with the broader community.
Brex earns fees, including distribution/referral fees (also known as 12b-1 fees) from money market mutual funds that are included in the Brex Cash sweep program.
> Ok, you won't sell it; but will you give it to third parties (even without payment) without the consent of the subject beyond the extent required by law?
[I work at Brex, and I’m not a lawyer :)]
Yes, you’re right in that we work with a small number of 3rd party systems which go through a rigorous screening, much of it focused on how they store and secure data. These systems are either for internal monitoring (e.g., system logging), or for running the business (e.g., KYC).
> What protections are in place to protect customers financial transaction information and will that information be sold, lent, or shared with any outside parties?
[I work at Brex]
Data privacy is something we’re really passionate about. We’ve had strong stance internally since we launched the Brex card, and a few weeks ago we made that publicly available, in a very transparent way (https://brex.com/privacy). Tl;dr: we do not and will not sell any personal information.
We’ll be expanding support for businesses in other countries throughout 2019. If you submit an interest form for the beta on stripe.com/terminal, we’ll be sure to let you know when we’re in the UK.
Apologies for the delay! Stripe Terminal works with our pre-certified card readers. This ensures that your transactions are secured by our end-to-end encryption and that your readers are always up-to-date via our remote management tools. We’ll share even more information about how we help reduce your PCI scope with Stripe Terminal when we launch full docs later this week!
Stripe Terminal gives developers the flexibility to build custom point of sale applications that use the Stripe payments platform, with EMV-ready hardware. The product will be work across the entire suite of Stripe products (Billing, Radar, Sigma etc.), and we’ll provide native SDKs across several languages.
We are excited about the use cases of Connect platforms integrating Stripe Terminal! We have seen a lot of platforms like AtVenue and Mindbody building an end-to-end solution for their users -- completely on Stripe.
Excited to review your application! We have a lot of users building point of sale applications for booking and scheduling -- including AtVenu, Mindbody, Universe, Zenoti.
We currently support two devices and will add support for more in the months to come. Please request an invite and let us know if there are particular hardware devices you are interested in us supporting.
The end consumer will have a seamless experience between paying online and offline -- think buy things online, return in-store (or vice-versa). Your customers can initiate a subscription in-store that continues online with Stripe Billing. You will have all your reporting -- for both online and in-person transactions -- within the Stripe Dashboard. In terms of customization, we think our new SDKs will make it really easy for you to build the right checkout experience for your business. Also, you’ll be able to customize some aspects of the reader display (e.g., logos, color theme, splash screen, etc.).
But that also doesn't mean we never evaluate what makes most sense for us as we continue growing ourselves. We have >400 engineers at Brex, so many things internally have had to evolve over the years, including our decision to build things in different languages (we now additionally support Go, Kotlin, Python & TypeScript, each for specific domains).
Even as we write more backend services in Kotlin, Elixir will continue existing for a long time, and we're continuing to work close with the broader community.