Blog

Follow Stripe on Twitter

Instant Payouts for Marketplaces

Dave Coen on September 19, 2016

Starting today, marketplaces using Stripe Connect can send Instant Payouts to sellers or service providers on their platform. To start, it’ll be available to marketplaces in the U.S. using Managed Accounts.

Unlike traditional bank transfers that can take several days, Instant Payouts are deposited and available in just minutes. This way, marketplaces can give service providers a much better product experience by sending them their earnings faster than ever—and greater flexibility and control over when they get paid.

We’ve been testing Instant Payouts as a beta with platforms of all sizes, including Lyft, Instacart, goPanache, Postmates, and Care.com. Across our beta users, service providers for on-demand marketplaces are thrilled to receive earnings faster.

Lyft, which was the first platform to integrate last November, has already sent over $500 million to drivers using Instant Payouts. In fact, Lyft now sends the majority of its driver payouts instantly—the only ridesharing company to do so. (Check out what Lyft driver Justine had to say about Lyft’s Express Pay.)

Here’s how it works:

  1. Collect debit card details: An increasing number of marketplaces are building their payout flows around debit cards. Bank details are hard to dig up and error-prone, but everyone has a debit card in their pocket. (Stripe will also automatically verify the details when a debit card is added.) Instant Payouts can be sent directly to service providers’ debit cards and funds are automatically deposited into the bank account linked to the debit card.
  2. Let sellers request Instant Payouts: Platforms typically offer Instant Payouts as an option in addition to their regular payout timing. Marketplaces can also customize when service providers can request a payout to their bank accounts. For example, Lyft offers an instant payout option in addition to their weekly transfer—and only once a driver earns $50.
  3. Send the payout: For the vast majority of payouts, funds are deposited within minutes. Initiating an Instant Payout requires just one additional parameter when creating a transfer:
curl https://api.stripe.com/v1/transfers \
  -u sk_test_jId8tWpQJuUpj7dtRQnkyH3t: \
  -H "Stripe-Account: acct_102lvT2rmKZAYQkm" \
  -d amount=5184 \
  -d currency=usd \
  -d destination=default_for_currency \
  -d description="Transfer to peter.r@example.com" \
  -d method=instant

Check out our docs for more details on how to integrate. Instant Payouts cost 1.5% of the payout amount, with a minimum fee of 50¢.

We’ve consistently heard from marketplaces of all sizes that attracting (and retaining) more service providers is crucial for growth and that this is often the tougher side of the marketplace to build. We’ve already seen that offering Instant Payouts has helped our beta users achieve that goal and we’re looking forward to more marketplaces enabling this feature soon.

If you have any questions, feedback, or need help getting started, please email me!

Everything marketplaces need to get sellers paid. Explore Stripe Connect

September 19, 2016

Get ready for Apple Pay on the Web

Charles Francis on August 29, 2016

Update: We’ve now published our full guide for Apple Pay on the Web. Get started with your integration by reading our docs.

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.

Today, we wanted to give a quick overview of the steps that will be required to support Apple Pay on the Web to help you prepare for its release:

  • Register your domain

    In order to prevent fraud, you’ll need to register the domain of your checkout page with Apple. You’ll be able to register your domain directly in the Stripe Dashboard, which lets you skip all the steps that’d otherwise be required, like manually provisioning and generating certificates in your Apple Developer Account. You’ll also be able to register multiple domains easily via our API.

  • Check for Apple Pay support

    We’ll be updating Stripe.js with a handy function to check whether your customer can use Apple Pay. (To start, Apple Pay will only be available in Safari to macOS Sierra and iOS 10 users.) The check will involve a straightforward conditional:

    Stripe.applePay.checkAvailability(function(available) {
      if (available) {
        // Display the Apple Pay button
        // Add a click listener to present the payment dialog
      } else {
        ...
      }
    });
  • Customize the payment form

    We’ll support all the fields you can use to customize what shows up in the Payment Sheet (the dialog that presents the transaction’s details to the customer). At minimum, you’ll just need to provide the amount to charge and the currency:

    var paymentRequest = {
      currencyCode: 'usd',
      total: {
        amount: '217.49',
        label: 'Warby Parker'
      }
    };

    As you’d expect, you can also use the Stripe integration to get your customers’ shipping info via Apple Pay or charge on a recurring basis for subscriptions.

  • Create a charge

    If you use Stripe.js, no sensitive data will ever hit your servers—we’ll handle creating secure sessions with Apple, decrypt the payment info, and pass along a token that you can use to create a charge.


You can sign up to be notified as soon as Apple Pay on the Web is available—we’ll be sending our full guide first to people on this list. In the meantime, if you have questions about Apple Pay (or Stripe in general), please drop me a line!

Get ready to support Apple Pay on the Web. Create a Stripe account

August 29, 2016

Why some businesses aren’t allowed

Danika Lyon on August 12, 2016

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.

That said, we provide financial services, and there are consequently a non-trivial number of restrictions regarding the use of our products. These restrictions have always been outlined in our Services Agreement, which we’ve tried to make as readable as possible. Given that they’re often a source of confusion, though, we figured it could be useful to try to explain some of the broader context around them and to describe the approach we want to take.

Why can’t we work with some businesses?

Behind the scenes, we work closely with payment networks (such as Visa and Mastercard) and banking partners across more than two dozen countries. Each institution has strict legal regulations that govern them and specific rules about the types of businesses they do and do not work with. Through our partnerships, we are bound to uphold those requirements. In addition, we must also—of course—uphold the laws of the countries we operate in. Lastly, we need to be careful regarding the financial risks that different businesses may pose to their customers or to Stripe.

In software terms, this is a leaky abstraction. In our ideal world, businesses using Stripe needn’t worry about how payment systems are implemented underneath the hood. In practice, however, every payment involves multiple financial companies whose restrictions may manifest themselves in Stripe.

As a result, the decision to support a business is not solely up to Stripe; it involves the various financial companies in the credit card processing chain. Their restrictions tend to be broad and, as a result, often pretty confusing.

Why are entire business categories prohibited or restricted?

Rather than evaluate each business in isolation, many financial institutions choose to make decisions around broad categories of business. Below are a few categories that are often restricted or prohibited from accepting payments. As you can see, the restrictions can function more like hammers than scalpels—tools designed to bluntly manage risk, not support the maximum number of businesses possible.

  1. Illegal businesses

    This one’s pretty straightforward. Quite simply, Stripe can’t support businesses selling or supporting illegal products or services. Many financial institutions enforce a blanket-ban on products that are legal in some states but not others.

    Some businesses exploit short-lived legal loopholes: for example, trivial drug variants that aren’t illegal yet. These are generally more hassle than they’re worth for everyone involved.

  2. Regulated businesses

    Some businesses live in heavily-regulated spaces and are only legal if compliant with the industry-specific rules. These rules can at times be difficult to verify and enforce online: for example, are we confident that an online pharmacy is checking prescriptions or whether a liquor store app is carding people? (How do you even card people online?)

    We can often support these businesses! It just takes more work. More on this later.

  3. Shady businesses

    The credit card industry is successful because consumers are confident that using their credit cards will be safe and predictable. By extension, they expect that the product or service they purchase will be of high quality and delivered as promised. Businesses that consistently leave their customers unhappy are bad for the overall integrity of the payment network. Because of that, some consistently-troublesome categories are restricted even though they may be within the law.

    We assess these businesses individually by looking at how the business is marketed, analyzing what is being sold, and by monitoring ongoing dispute rates by customers. We don’t support businesses that consistently deceive customers or leave them unhappy.

  4. Financially-risky businesses

    If a business becomes insolvent and fails to deliver goods or services it has already sold, Stripe loses money: the business’s customer can initiate a chargeback and Stripe covers the loss. This is a bigger risk in businesses with a very long wait time between purchase and delivery, or in pre-sales of highly speculative or pre-production products.

    We look at businesses individually to determine the overall level of financial risk based on industry, stage of product development and shipment, and overall exposure. We’re familiar with newer business models (like crowdfunding) and do our best to be permissive. If you’re going to be accepting large amounts of money for a product or service that’ll be delivered much later, it’s always better to get in touch with us first.

  5. Businesses that attract money-laundering or fraud

    Most service providers aren’t required to closely police usage of their services. Financial institutions, however, are obliged under US and international law to actively monitor usage to prevent money laundering and other criminal activity.

    Some types of businesses attract more fraud than others; others accidentally or deliberately mask the origin of funds, making them an easy venue for illegal dealings. Businesses in these categories are not inherently problematic, but might need extra scrutiny or extra help in preventing fraud.

  6. Businesses that pose a brand risk

    Financial institutions and payment networks care about the brand and reputational risk that associated businesses pose. There are a set of businesses that our financial partners do not want to be associated with even if there is market demand for them. Stripe doesn’t independently reject businesses based on brand risk—we have many unpopular businesses and causes on Stripe—but we’re at times obliged to enforce the restrictions of our partners. This category is highly subjective and therefore the one we like enforcing least.

    We don’t think Stripe should be accepting or rejecting businesses based on a subjective determination of brand impact, and we feel the current brand restrictions (such as on sex toys) are often outdated and overly moralizing. We have only had limited success in supporting businesses in this category; there are many legitimate businesses we can’t support. Over time we hope to broaden the set of businesses in this category that we can support.


Stripe’s approach

We want to grow global online commerce and support as many businesses as possible—especially those based on new business models or founded by first-time entrepreneurs. Wherever possible, we eschew risk assessments based purely on categorical labels. Instead, we use a combination of transaction history, machine learning, supplemental business information, and common sense. We want to understand the actual risks posed by a specific business, with the fundamental goal to support as many businesses as possible, rather than just looking at the industry or category. We work with our financial partners to relax restrictions or remove prohibitions wherever possible.

Here are a few examples of niches where we’ve successfully worked past unnecessary restrictions:

  • Marketplaces

    Historically, many payment companies have been leery of marketplaces that "aggregate" funds on behalf of other sellers due to the possibility of fraud or money-laundering. But avoiding marketplaces would mean failing to support many of the most exciting businesses of the last decade: new business models like crowdfunding (Kickstarter, Indiegogo), commerce platforms (Shopify, Squarespace), and on-demand services (Lyft, Postmates). Multi-sided marketplaces are clearly legitimate businesses providing useful coordination services for consumers. Stripe built Connect, one of the first products that serves as a compliant way for marketplaces (including all of those mentioned) to operate at scale and ensure that any money collected on one side was paid out to the correct parties on the other sides.

  • Alcohol

    The 21st Amendment to the U.S. Constitution left the responsibility of repealing the 18th Amendment (Prohibition) to individual states. The result has been a dizzying array of local, state, and federal laws, as well as a 3-tier system (producers, distributors, retailers) where each has different regulatory responsibilities. As more commerce moves online, customers and businesses are interested in buying and selling alcohol online. Stripe saw legitimate businesses (like Broc Cellars and 750 Commerce) unnecessarily impeded by the effects of antiquated local alcohol regulations.

    750 Commerce is a platform that provides website design, development, and direct-to-consumer wine order management for upscale wineries. Stripe worked with 750 Commerce to address specific regulatory concerns including state-to-state shipping and age verification at delivery. Broc Cellars ran into similar complications for its wine club and we addressed concerns including confirmation of licenses, marketing, and importantly, age verification at delivery. In each case, we enabled direct to consumer online alcohol sales.

  • Pharmacies

    The payments industry has traditionally assumed that "internet pharmacy" was code for illegal business, often operating cross-border, selling highly-controlled prescription drugs such as Vicodin, Valium, and Viagra without prescriptions or without appropriate medical supervision. As such, credit card networks imposed stiff restrictions that led to an exceedingly high bar to starting a technology-enabled community pharmacy.

    PillPack is a startup that delivers a better full-service pharmacy experience over the web. We worked with our partners to determine the necessary qualifications to support online pharmacies including qualifying exceptions, licenses and certifications, internal controls, and VIPPS registration. Once we identified the necessary requirements, we partnered with PillPack to verify and get approval for the business. Since then, we’ve advocated for several other online pharmacies: ScriptDash and NowRx both run on Stripe. Supporting on-demand community pharmacies is still a work in progress and we’re working to make this process faster, easier, and more transparent.

  • Pseudo-pharmaceuticals

    femMED was founded in 2007 to empower women to take a more natural approach to health and wellness. femMED has a nine-year history of helping women and has created 24 different licensed natural health products. Pseudo-pharmaceuticals are another historically-restricted category because of untested or unapproved products and exaggerated claims that often accompany the products. But we saw a business that had superb customer satisfaction, proven track record, and honest marketing claims. We highlighted the processing history and product approval by Canada’s natural health regulatory body that directly addresses key concerns of this industry and our financial partners agreed. femMED is the first (of hopefully many legitimate) supplement businesses that we can support.

  • Travel

    Technology companies like OpenJet run into the same objections that banks tend to raise for airlines: customers book far in advance and the credit risk is significant. Travel is a broadly-prohibited category because airlines and cruise lines present enormous credit risks in payments due to a history of bankruptcies and insolvencies of U.S. airlines. (TWA, Pan Am, United, American Airlines, and many others have all gone bankrupt at some point.)

    We recognized that the private jet market is different and analyzed financial statements, payment flows, customer profiles, and more to fully understand the underlying mechanics of the business. We modeled OpenJet’s business and determined that the credit exposure was within an acceptable range. We engaged our banking partners with concrete financial analysis, put in controls to monitor risk as the company grows, and OpenJet successfully launched on Stripe.

  • Adult products and services

    OMGYes is a sex-ed startup that conducted the first-ever large-scale research about women’s sexual pleasure in partnership with researchers at Indiana University and The Kinsey Institute. OMGYes decided that instead of writing another book with the results of the study, they’d create a website to provide honest, actionable information about sex and women’s pleasure. The website was endorsed by Emma Watson and was recently featured in Elle, Forbes, and Wired. The business approached us and we were eager to work with them, but after a month of deliberations, our financial partners did not agree. Instead, because the website has explicit tutorials, it still falls under the umbrella of unsupportable businesses. While we were not able to persuade our financial partners this time around, we will continue to holistically look at and advocate for businesses that sell adult products and services.


What this means for you

While Stripe lives in a tangled thicket of regulations and restrictions, we want to support as many businesses as possible. We have a dedicated team of friendly risk and compliance analysts, support personnel, and financial partner experts for this very purpose.

We’re here to make it easier for great new ideas to be implemented. If you’re building something cool and innovative, we want to help support you. If that idea ostensibly falls into one of our restricted categories, please get in touch with us! We’ll do whatever we can to help.

August 12, 2016

Managed Accounts in Europe

David Schreiber on July 5, 2016

Today, we’re thrilled to launch Managed Accounts for Stripe Connect to marketplaces based in the U.K., Ireland, Sweden, Denmark, Finland, and Norway.

Connect powers thousands of marketplaces around the world—companies like Kickstarter, Lyft, Shopify, and Deliveroo that are transforming the way we buy and sell today. With Managed Accounts, marketplaces like these can fully customize the experience for sellers or contractors that provide the services on their platform.

Using Managed Accounts, multi-sided marketplaces in Europe can now design lightweight setup flows, configure payment schedules, decide who pays fees, determine when information is collected, and more. Stripe gets out of the way so your sellers never have to leave your platform.

You can craft fully-customized signup flows and dashboards for service providers on your marketplace.

Since the launch of Managed Accounts in the U.S. and Canada last year, we’ve already helped millions of sellers get paid. We’ve worked over the past year to ensure that the experience of building, running, and scaling your marketplace is as easy as possible no matter where your business is based:

  • Just like U.S. and Canadian platforms, marketplaces in Europe can now spin up Managed Accounts for sellers or contractors in any of the 25 countries that Stripe supports today without having to register a local business entity or establishing banking relationships in each region—a process that can take many months and reams of paperwork. In other words, you can instantly expand your business internationally to new countries without having to build payments infrastructure to meet local requirements.
  • You’re also no longer required to acquire licenses or decipher per-country compliance intricacies by yourself. Stripe will help you verify seller identities (to comply with know-your-customer laws and prevent fraud), collect and verify your sellers’ banking information, track seller earnings, help sellers get paid on the right schedule (and in their preferred currency), help handle tax reporting requirements, and more.

Modern marketplaces are building more than just simple apps; they provide an end-to-end experience for both consumers as well as the drivers, restaurants, sellers, or contractors on their platform. We’re excited to see the experiences entrepreneurs in the U.K., Ireland, and the Nordics will build with Managed Accounts and how they’ll use Connect to scale internationally not only in Europe, but around the world.

If you’d like to learn more about how to integrate, we’ve put together a guide to getting started. We’re also constantly adding improvements and support for more countries to Connect, so if you have questions or feedback, please drop us a line!

Learn more about Connect Get in touch

July 5, 2016

UI components for iOS

Jack Flintermann on June 30, 2016

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 pre-built components drastically reduce the time needed to create beautiful, high-conversion iOS checkout flows.

We’ve introduced a new class called STPPaymentContext that is designed to make building your app’s checkout flow as easy as possible—and without having to code it from scratch. To start, some of the pre-built components include:

  • Adding cards: Make it easy for your customers to save card details in your app to use for future purchases. We’ll also handle tokenizing the card info so that sensitive data never hits your servers.
  • Editing cards: Smarter Saved Cards will keep most card details up-to-date automatically, even if they expire or change. You can also let customers manually edit their card info within your app.
  • Billing info: Use our pre-built, native forms to collect addresses from customers.
  • Apple Pay detection: The SDK now configures your app to automatically fall back to a native flow if Apple Pay isn’t supported on the customer’s device. (Previously, you had to manually check for Apple Pay support before presenting either flow.)

These UI components have already been crafted to fit into most apps’ look and feel on iOS devices. Additionally, you can customize the font, as well as background, foreground, and tint colors to match your app’s unique design and make the experience as seamless as possible for customers.

We’ve learned from thousands of the most innovative apps on Stripe—Lyft, Kickstarter, Instacart, OpenTable, and more—to build best practices into these UI components. We’ll also be adding more flows and optimizing the ones launched today over time.

If you’re interested in using these new components, we’ve put together a guide to getting started, which also includes instructions on upgrading to the latest version of the SDK.

As always, if you have questions or feedback, please let me know!

June 30, 2016

Atlas update

Taylor Francis on June 24, 2016

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.

Atlas companies are tackling a broad swath of challenges and industries. Almost all of them are creating products or platforms that can be used by customers around the world. We thought it would be interesting to share just a few examples of the kinds of businesses we’ve been working with so far:

  • Trakto is a software-as-a-service company from Brazil that helps small businesses and freelancers to design, share, and track marketing materials. Inhibited by complex local tax and regulatory policies, Trakto’s founder Paolo Tenorio Filho couldn’t accept payments from international customers. (For the local payments they could accept, Trakto had no option but to manually invoice their clients.) You can read more about Trakto’s challenges in Paolo’s post on his experience with Atlas.
  • Coterique is an internet marketplace for fashion designers. Before Atlas, the Cairo-based startup was restricted to accepting payments in Egyptian pounds. Now, Coterique can accept any currency and use Connect to automatically pay out to international designers on their platform.
  • With Atlas, the Kenyan startup Ongair, which allows businesses to manage customer service via instant messaging platforms, now reaches customers around the world. Trevor Kimenye, Ongair’s CEO, is also finding that initiating conversations with U.S. investors for their upcoming Series-A round is a lot easier.

These companies are ambitious. Over 75% intend to raise funding from investors and in aggregate they plan to double their headcount over the next 12 months. The interest in Atlas, and the calibre of companies currently being built by Atlas entrepreneurs, underlines that there’s a lot of work left to expand access to fundamental startup tools to as many developers around the world as possible.

To that end, we’ve now added over a hundred accelerators, investors, and partners to the Atlas Network. These partners are helping us get Atlas into the hands of the most promising startups. We’re also working with financial institutions, leading tax and legal firms, and with the U.S. government.

We’re working through the waitlist and scaling the Atlas product experience to more users as quickly as possible. In the meantime, please reach out if you have questions or feedback! And, most importantly: if Atlas can help you build a global company, don’t hesitate to apply.

Get access to global startup tools with Stripe Atlas Request access

June 24, 2016

Native support for taxes and shipping

Rasmus Rygaard on June 21, 2016

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:

Calculating taxes

Working with customers across many countries can often translate to maintaining complex lists of rules for taxes (state taxes, VAT, GST, and more). Until today, we’d left calculating taxes as an exercise for the reader. Now, we’ll help automatically calculate taxes—just supply your customer’s address when creating an order. (You can also specify a customer object and we’ll look up the address.) Here’s a quick example of creating an order:


  curl https://api.stripe.com/v1/orders \
     -u sk_test_BQokikJOvBiI2HlWgH4olfQ2: \
     -d items[][parent]=sku_8XOBjVaulB0SWy \
     -d customer=cus_4A5UNnP8WgZa91 \
     -d currency=usd

  {
    "id": "or_17pkOFDAu10Yox5ReR89xhT1",
    "object": "order",
    "amount": 7524,
    ...
    "items": [
      {
        "object": "order_item",
        "amount": 525,
        "description": "CA STATE TAX (PC040100)",
        "type": "tax",
        ...
      },
      ...
    ]
  }
  

As you can see, the response includes the total for the order, including the tax required for that particular customer. To make this work, we’ve partnered closely with both Avalara and TaxJar to build integrations that effectively take care of the calculations for you. They also take on the work of maintaining a canonical (and extensive!) database of tax rules.

This works for customers in any country and you’ll also be able to view detailed reports, which include liability calculations to help with your tax reporting.

If you’re interested, we’ve put together guides to getting started with both Avalara and TaxJar. You can enable either integration from your Dashboard.

Calculating shipping costs

Relatedly, calculating shipping also used to require maintaining lists of fees for different products, carriers, and countries. Now, instead of building your own lookup system for shipping costs, we can use the weight and dimension info from your product to automatically return shipping costs when you create an order. Of course, you’ll also need to specify your origin location and the destination address.

To start, we’re working with EasyPost and Shippo to power accurate shipping cost lookups across major carriers like UPS, FedEx, DHL, and more. You can activate the integration in your Dashboard.

Sync product feeds with Stripe

The taxes and shipping calculations rely on having up-to-date product info in Stripe. Currently, many Stripe users either manually add their products to Stripe via the Dashboard or through a repeating upload using the API. To help, we’re now also adding support to automatically keep your products in sync with Stripe using a product feed.

We’re starting by adding support for importing Google Product Feeds as well as Linkshare Data Feeds. (If you retarget customers via display networks, you likely already have a product feed in a format Stripe can parse.)

You can manually import your products to get started and schedule a daily or weekly import depending on how frequently you update your feed.


We hope these updates will help simplify your work to calculate shipping and taxes. Since these integrations are built on Stripe’s open platform, we expect to add more partners for taxes, shipping, and many other features in the future to make running your business on Stripe even easier.

As always, let us know if you have questions or feedback!

June 21, 2016

Stripe en France

Guillaume Princen on June 8, 2016

Français English

Today, we’re happy to remove the beta label and to make Stripe available to tout le monde in France.

We’ve been testing Stripe in France for over a year and have already had thousands of French businesses start building on the Stripe platform. Companies like Withings and Dailymotion, SaaS platforms like Algolia and Dashlane, and even marketplaces like Drivy and KissKissBankBank. We’d like to thank them and the many others who have shared their feedback and suggestions along the way.

Everyone in France can now sign up in minutes and get access to the world-class Stripe stack that we’ve been building and optimizing for more than five years. Developers can charge customers in 100+ currencies (and a growing set of payment types), create subscriptions, or build global platforms with Stripe Connect. Pricing is simple and predictable: 1.4% + €0.25 for European cards and 2.9% + €0.25 for non-European cards.

We’ve also built a local team and now provide support for our users in French as well. Our France team hails from all across the country—Paris, Lyon, Avranches, and even the booming metropolis of Figarella in Corsica. Our office is based in the 2nd arrondissement in Paris.

Now that Stripe is publicly available in France, we’re looking forward to seeing all the new products and services that French entrepreneurs will develop with Stripe. We’ll be continuing to make changes to improve our service in France—drop us a line or tweet at @StripeFrance if you have any questions or feedback.

Lastly, we’re also hiring! Please get in touch if you’re interested in working with us on building the payments infrastructure of the internet.

Start accepting payments instantly in France. Get Started with Stripe

June 8, 2016

iOS and Android updates

Jack Flintermann on May 27, 2016

Over the past few months, we’ve made a few changes for iOS and Android that might be useful for your apps:

NewApple Pay in Canada, Australia, and Singapore

In addition to customers in the U.S. and the U.K., you can now accept payments in your app via Apple Pay from customers in Canada, Australia, and Singapore.

NewAndroid Pay in the UK

As announced at Google I/O last week, you can now accept payments using Android Pay from customers in both the U.S. and the U.K. (We’ve put together a guide to get started.) You can also sign up to get notified when it’s available in Australia and Singapore.

NewSupport for Discover cards

We’ve added support for Discover cards to both Apple Pay and Android Pay. If you’re currently accepting Apple Pay payments, just update to the latest version of our SDK. No changes are required to your Android app.

NewMobile viewport control

We recently released an open-source JavaScript library that helps create full-screen modal views in mobile browsers. This can be especially useful in displaying a distraction-free payment screen, but we hope it comes in handy for other uses as well.


While we’re talking about mobile things, we’ve been adding all sorts of polish and tweaks over the past couple of months to our iPhone Dashboard. For example, if you’ve any transfer issues, we now show a tappable link to call your bank. And based on your feedback, we’ve also added a weekly view to your account charts.


Feedback is always always welcome—we’d love to hear any thoughts on the above, or about anything else you think we should add that’d make building mobile apps with Stripe better.

May 27, 2016