Blog

Suivre Stripe sur Twitter

A Pricing Update

Patrick Collison on December 19, 2012

Update: For the latest, up-to-date information on pricing and fees, please see our pricing page.

We’ve always believed in simple, low prices. In this vein, we’re making two changes today:

New No fees on refunded charges

When you refund a transaction, Stripe will return the entire fee. Until today, if you charged $100 and then refunded the transaction, it would still cost you $3.20—that is, 2.9% + $0.30. From now on, it will be free.

New No fees for successfully-challenged disputes

If one of your customers disputes a payment, Stripe charges a fee of $15. However, you have the option of challenging the dispute. If that’s successful, and the cardholder’s bank decides in your favor, we’ll now refund that $15.

Both of these changes go into effect immediately.

December 19, 2012

Two-Step Verification

Ross Boucher on December 13, 2012

It's a dangerous world out there! But you can make things a little bit safer by turning on our new two-step verification setting in your Stripe account settings.

Once you do, you'll need a code generated on your mobile device any time you log in to your Stripe account. You'll also be asked for this code once every two weeks when taking sensitive actions like viewing your account settings, or issuing a refund.

How do I enable two-step verification?

You can enable two-step verification in your Stripe account from your account settings. Download the free Google Authenticator mobile app (available for iOS and Android), and click on the enable button. Scan the barcode on your screen with your mobile device, and finally type the code on your device to finish the process.

At the end of this process, we'll show you your emergency backup code. Make sure to write down this code and store it somewhere safe. If your mobile device is lost or stolen, you can use this code to disable two-step verification on your account. Without either your device or this code, you won't be able to log in to your Stripe account.


Of course, two-step verification is just one useful tool in keeping your account secure. You should also make sure to follow other password best practices, like using long passwords that don't contain personal information, and using different passwords for each website.

December 13, 2012

Hack to the Future

Amber Feng on November 20, 2012

Join us at the Stripe office for a day of hacking and time-traveling1. Hack on a project, meet other coders, hang out, or just work on eating the food.

We're trying something a little different this time: while the hackathon will still be informal and you're welcome to hack on anything you'd like, we're encouraging projects built on top of Stripe Connect.

Stripe Connect, released a little over a month ago, uses OAuth to make building apps on top of Stripe data or allowing your users to accept payments easy. Some existing applications include store-builders, marketplaces, and data analytics dashboards—we're really excited to see what other ideas people come up with.

If you've been meaning to play around with the Stripe Connect API, this is a perfect time to check it out or meet others who'd love to collaborate. The team will be around to help you with the integration and answer any questions you may have. Beginners welcome!

When:
Saturday, December 1, 2012
from 1:00 PM until 10:00 PM
Where:
Stripe's office at 140 Second Street in San Francisco, 4th Floor.

RSVP via our Meetup event. Hope to see you there!

1: Bring your own DeLorean.

November 20, 2012

API Mailing List

Ross Boucher on November 16, 2012

As we grow, we're constantly refining our API by adding new capabilities and sometimes by removing or replacing features that aren't working as well as we'd like. To make these changes easier to follow, we've created a new mailing list, available on Google Groups. Going forward, we'll send updates to this mailing list any time we add or change something in the Stripe API.

Whenever we change our API, we make every effort to ensure we won't cause problems for any of our existing users. One of the main ways we maintain backwards compatibility is by marking accounts with specific flags that tell our API to return an older version of a particular response, or enable an older set of input parameters. New users immediately get the new behavior, and we can work with our existing users over time to upgrade their Stripe integrations.

This same system works with Stripe Connect, to ensure that an application accessing many Stripe accounts can still work with a consistent API, even if the individual accounts use a different set of flags when talking to Stripe on their own. If you aren't using Stripe Connect, but you are still working with code used across multiple Stripe accounts (e.g. a Stripe API library), you may need different code for some accounts. If so, it is especially important to sign up for this new list to be updated about changes.

November 16, 2012

Better Dispute Management

Sheena Pakanati on November 15, 2012

We’re trying to make every part of payments easier, and that includes oft-neglected pieces like handling disputed charges (also known as chargebacks). We’ve just launched some new features to help you manage your disputed charges:

New API for retrieving and updating dispute details

Disputed charges now have a dispute attribute that provides you with details about the dispute. You can also update dispute evidence via the API, which should be especially handy for Stripe Connect users who need to manage disputes on other Stripe users’ behalf. The API exposes everything you need to know about the dispute, including the status and an easy-to-understand reason for the dispute if we have it.

Note: Currently the disputes API only includes complete dispute data starting from September 23, 2012.

New Managing disputes in your dashboard

You can now peruse a full list of your disputes, filter them by reason or status, tell at a glance what disputes need your attention, and see details about any individual dispute.

Responding to a dispute is also much easier than before: just visit your dashboard to submit evidence. We’ll even suggest what specific details to provide — based on the disputed charge and the cardholder’s reason for disputing it — to increase your chances of winning the dispute.

New Better charge dispute events

We’ve added three useful dispute events: charge.dispute.created (when a charge first gets disputed), charge.dispute.updated (when a dispute’s evidence is updated), and charge.dispute.closed (when a dispute is resolved, either in your favor or in the cardholder’s favor). If you’ve no need for webhooks, don’t worry: we’ll still send you an email when a dispute is created or closed.

Note: On Dec 15, 2012, the old charge.disputed event will be deprecated.

Our goal is to work with our users to make sure that disputes don’t arise in the first place, and we hope that you don’t have frequent occasion to use these new features—but we hope they’ll make your life easier when you need them.

November 15, 2012

Live at General Assembly

Saikat Chakrabarti on November 13, 2012

Our friends at General Assembly are hosting a free livestream class on integrating payments using Stripe, and you're invited!

We've worked together with them over the past week to put together a tutorial that takes you from accepting payments on your website to setting up subscription billing with webhooks. Chris Castiglione will be using the tutorial to teach the hour-long class, and he will be answering questions live during the event.

So if you're just thinking about building a new business or already have a website or mobile app and want to start accepting payments, tune in. You can find the full details of the event here.

When:
Wednesday, November 14, 2012, at 2:00 PM (EST)
Where:
Zum Schneider

Sign up to get a link to the livestream.

November 13, 2012

Stripe + Wufoo

Cristina Cordova on October 23, 2012

We recently launched Stripe Connect, a straightforward way for sites to enable payments for their users, and for Stripe users to share their data with other services. Wufoo recently integrated Stripe Connect, and we want to take a moment to show you how it works. It’s a great example of what’s now possible with Stripe Connect.

Wufoo makes it easy for anyone to create beautiful forms in minutes, with no technical expertise required. With Stripe Connect integration, you can now use Stripe to accept payments directly on your Wufoo form—perfect for managing event registration, taking orders online, accepting donations, and much more.

How it Works

Wufoo handles the database, backend and scripts needed to make collecting and understanding your data easy and fast. Once you’ve created your form, head over to your Payment Settings to connect with Stripe:

As soon as you’ve enabled payments with Stripe, your customers will enter their credit card information directly on the form, and won’t be redirected to a checkout page. Wufoo will collect the data on your form, and Stripe will take care of transferring your payments directly to your bank account.

We’re thrilled to partner with Wufoo. Explore their documentation to learn how to start accepting payments with Stripe, or how to migrate your existing payment-enabled Wufoo forms.

Wufoo + Stripe is just one example of how you can build on top of Stripe for the benefit of your users, and we look forward to seeing what others create. Read more about Stripe Connect or head straight to the docs.

October 23, 2012

Stripe Connect

Amber Feng on October 10, 2012

Today, we’re proud to launch Stripe Connect, which adds two important new capabilities to Stripe: a straightforward way for sites to enable payments for their users, and a seamless mechanism for Stripe users to securely share their data with other services.

Stripe for your users

Some of the most innovative businesses on the internet help others become sellers: store builders, website creators, marketplaces, and many more. In the past, figuring out how to make payments work has been a big barrier to building these kinds of companies—there hasn’t been any good way to immediately facilitate credit card transactions for sellers.

And yet these sellers—the platforms’ users—are often the people who most need a simple way to accept payments online. They’re the people just starting out, focused on getting their business off the ground. By integrating Stripe Connect and having users link with a Stripe account, any service can enable their users to start accepting payments in minutes. This is a big change, and by streamlining this process, we hope to help increase the number of people selling online.

Unlocking data

Stripe Connect also enables people already receiving payments with Stripe to link their accounts with other services, making it straightforward for developers to build rich tools that integrate payments data. Anyone using Stripe today can already export their data in CSV or JSON. Stripe Connect facilitates secure sharing of this data with third-party applications. Users can grant either read-write or read-only access to their data, and can revoke the authorization at any time.

Up to now, a business’s transaction data has usually remained siloed and inaccessible. We think it should be easy to safely share payments information with accounting software, analytics tools, and CRM systems—imagine tools that magically generate a tax return, make it easy to tie your web analytics to your purchases, or that show a user’s pricing tier in your customer support system.

Since we can't tackle every conceivable use-case ourselves, we want to encourage an ecosystem where anyone can build applications that leverage Stripe data.

Building Stripe Connect

Fundamentally, Stripe Connect is a way for sellers to link their Stripe accounts with third-party services. It’s built on OAuth, the industry-standard federated login mechanism. However, unlike most OAuth implementations, we’ve also made it easy to create an account during the authentication process, since many people may not already have Stripe accounts.

Stripe Connect has been in beta for several months now. During that time, many companies have integrated its capabilities. These include ShopLocket, Shopify, Skillshare, Wufoo, Ballpark, Desktime, and SumAll. We deeply appreciate the feedback we’ve received from all of our beta users—they’ve shaped the product you see. We look forward to their launch of their integrations.

We’re still in the early days of figuring out the scope of commerce on the internet. At Stripe, we spend our time thinking about how to build better tools for the online economy. Stripe Connect brings some new possibilities to the web, and we can’t wait to see what people build with it.

Let your users connect with Stripe. Learn more about Stripe Connect

October 10, 2012

Towards Transparency

Jon Zieger on September 28, 2012

Over the past few years, a number of companies we admire—among them, Google, Twitter, and GitHub—have taken significant steps to increase awareness of the effects of the legal process on their users.

Stripe handles payments, but we believe similar thinking can be applied here too. Today we’re announcing two steps in this area:

First, we’re partnering with Chilling Effects. Developed at the Berkman Center for Internet & Society, Chilling Effects is run by the EFF and law clinics at Harvard, Stanford, Berkeley, and other universities across the country. Chilling Effects tracks the use of cease-and-desist notices to gauge the impact of legal threats to online expression. This database of notices provides important empirical data concerning the real-world effects of laws and policies.

From now on, whenever a third party sends a legal request for us to stop working with a user, we will pass a copy of the request to Chilling Effects. (We will, however, first give the user the chance to opt out of this disclosure.) Reporting take-down requests is standard practice at Google, Twitter, and GitHub today. Since Stripe is the first payments company to do this, Chilling Effects is creating a new category to track these requests.

Second, we’re updating our privacy policy to align with emerging internet best-practices. Specifically, we’re adding a clause that commits us (when possible) to first notify the user if we’re legally compelled by a litigant or government to disclose a user’s private information. The point of this notice is to give users the chance to contest the disclosure if they wish. As with publicizing take-down notices, this notification is becoming common when user data is in question, and we’re happy to join companies like Dropbox and Twitter in providing this protection for our users’ personal information.

These issues rarely arise, and there’s no particular situation that makes this timely. We simply want to implement the right policies as early as possible, and we intend to build on these steps over time. For example, we’re thinking about ways to make data and statistics available in this area, such as what Google has done with their Transparency Report.

Our goal with Stripe is to help build the economic infrastructure of the internet. Economic infrastructure, like other fundamental layers of the internet, requires trust and transparency. We hope these policies increase both.

September 28, 2012