Apple Pay on the Web will be available later this fall. (Apple has not yet published an exact date.) We’ve received a lot of questions about how the integration will work and we’ve been working closely with Apple to ensure that the implementation will be quick and easy for Stripe users.
We’re building business infrastructure. As with other kinds of infrastructure (like hosting or electricity), we'd like to make it available to as broad a set of users as possible. While we may personally like some businesses on Stripe and disapprove of others, we want to make as few judgements as possible as a company. The world doesn’t need more gatekeepers.
Today, we’re thrilled to launch Managed Accounts for Stripe Connect to marketplaces based in the U.K., Ireland, Sweden, Denmark, Finland, and Norway.
We’ve added reusable UI components in our latest iOS SDK that make it easy to accept both Apple Pay and regular credit card payments through a single, unified integration. The UI library supports automatically detecting Apple Pay, storing cards for future use, and custom styling. We hope these prebuilt components drastically reduce the time needed to create beautiful, high-conversion iOS checkout flows.
We announced Atlas a few months ago and we’re so excited by the amount of interest we’ve already received. Since launching the beta, over 440 startups from 91 countries are already using Atlas to get up and running with Stripe. More broadly, we’ve received applications from entrepreneurs in almost every country.
In the past year, we’ve added deeper support for representing products and orders to the core Stripe API. By working with products and orders, we can start to remove a lot of the unnecessary complexity that companies currently deal with—manually calculating taxes, figuring out shipping costs, or even just keeping product and inventory data in sync with all their systems.
Over the past few months, we’ve made a few changes for iOS and Android that might be useful for your apps: Apple Pay in Canada, Australia, and Singapore, Android Pay in the UK, support for Discover cards, and mobile viewport control.
Do you know anyone who makes you incredibly better at what you do? People who motivate and inspire you, complement your strengths and shore up your weaknesses, help you achieve things you could never do on your own? Maybe it’s your old cofounders, your college roommates, your collaborators on an open source project, or even your siblings; whoever it is, you’re stronger as a team than you are apart. Working together, each of you has a valuable advantage—you could call it a network effect—over anyone who works alone.
To keep your integration with Stripe secure, we plan to progressively phase out support for old technologies: SHA-1, TLS 1.0, and TLS 1.1. (These protocols currently power the ‘Secure’ in ‘HTTPS’.)
This January, we invited three developers to come work on open-source projects full-time at Stripe. We specifically chose projects for this Open-Source Retreat that we felt would have deep impact in a variety of different areas. Over the past few months, our grantees have made significant progress on their projects.
Even though there are many benefits, accepting ACH payments—that is, payments where you charge a bank account directly—has traditionally been pretty difficult. Doing so has generally involved baroque, legacy APIs. There’s additional complexity compared to credit cards because the transaction amounts are typically larger and authorization is subtler. Still, being able to handle ACH payments with Stripe has come up a lot as a feature request over the years. And so, today, we’re delighted to launch support for ACH payments for all U.S. Stripe users.
Like many developers, we often contribute to open-source software in bits and pieces over long periods of time. So we started the Open-Source Retreat to help open-source developers make concentrated progress on features and releases with the potential for significant impact. For 2016’s Retreat, we’re inviting three developers to work on their projects from Stripe’s office in SF.
We increasingly rely on (and contribute back to!) a lot of open-source software to build Stripe, and we’d like to give back and get more people working on open-source.
Last year, we invited four developers to the Stripe office as part of our first Open-Source Retreat. Our grantees made significant progress on their projects in a relatively short time. Starting January, we’re hosting another Open-Source Retreat at Stripe.
In February 2013, we blogged about email transparency at Stripe. Since then a number of other companies have implemented their own versions of it (which a few have talked about publicly). We often get asked whether email transparency is still around, and if so, how we've scaled it.
A few months ago, we announced our Open-Source Retreat. Though we’d originally expected to sponsor two grantees, we ended up giving out three full grants (and then an additional shorter grant).
We rely on a lot of open-source software at Stripe, and over time we’ve contributed back our own share of patches and projects. We decided we’d like to do more, though, so we’re launching an open-source retreat program.
People tend to have a narrow view of the problems they can solve using GDB. Many think that GDB is just for debugging segfaults or that it's only useful with C or C++ programs. In reality, GDB is an impressively general and powerful tool. When you know how to use it, you can debug just about anything, including Python, Ruby, and other dynamic languages. It's not just for inspection either—GDB can also be used to modify a program's behavior while it's running.
