The Dashboard officially supports the following web browsers and mobile environments:

• Chrome versions greater than 49
• The last two versions of Firefox, Safari, and Edge
• The last two versions of mobile Safari on iOS
• Internet Explorer 11

‍

The Dashboard is organized by the most common workflows used to manage your business. For example, the Payments section includes everything you need to manage the flow of money in and out of your account.

In many cases, you can use the Dashboard to perform specific actions, such as refunding a payment or canceling a subscription, without needing to use the API---making the Dashboard a useful tool for running your business.

‍

The Developers section of the Dashboard provides you with useful information about the performance and health of your integration. You can view your API and webhook usage with real time charts, upgrade your API version, and review API errors that can be filtered by endpoint or type.

‍

Stripe logs every successful or failed request made using your API keys. Each log contains details about the original request, whether it succeeded or failed, the response from Stripe, and a reference to any related API resources.

Every event that takes place on your account can also be reviewed in the Dashboard. Events represent a change to an API resource (e.g., a Charge object is created or updated), and contains its current information.

‍

Stripe and our hardware partners periodically release reader software updates, which can include improvements and required security updates. The Verifone P400 reader software updates automatically. The BBPOS Chipper 2X BT reader software must be updated manually. As reader software updates are made available, update your readers to the latest available version to continue using Stripe Terminal. Failing to install a required manual update can prevent a reader from accepting payments.

In-person payments must follow strict rules to meet PCI compliance, PCI certifications, and EMV certifications.

Terminal offers a selection of pre-certified, PCI-compliant readers that accept payment details (EMV, contactless, and swiped), encrypt sensitive card information, and return a token to your application through the Stripe Terminal SDK so that you can confirm payment.

‍

Before it can process payments, a Stripe Terminal reader must be connected to your point of sale application via the Stripe Terminal SDK. Each reader can only connect to one instance of the SDK at a time. For example, if your app runs on iOS and you want four mobile readers in your store, you also need four iOS devices.

‍

Stripe Connect provides a powerful API and other tools you need to accept payments, as well as onboard, verify, and pay sellers and service providers. You can tailor your integration in various ways, including:

• Specifying how money moves from the customer to you, and ultimately to your platform’s sellers or service providers
• Collecting fees for your service
• Assigning payout schedules and payout methods
• Supporting different types of Stripe accounts

‍

If you know what type of platform you’d like to build, we’ve written up some sample recipes for specific types of platforms:

• On-demand apps: building an app like Lyft or Handy.
• Store builders: allowing other people to sell on your platform, like Squarespace or BigCommerce.

Even if you’re not striving for one of those exactly, these examples should help you figure out how you’d implement yours.

If you’re building a service on top of Stripe account data—for instance, an analytics service like Baremetrics—read our guide to building an extension.

‍

Follow the steps below to get started. If you’re based in the U.S., Stripe will provide some guidance on capabilities and account types after you complete the first step.

1. In the Stripe Dashboard, click Get started to start the process for activating your account and registering your platform.
2. Determine the capabilities your connected accounts need (U.S.-platforms only).
3. Determine the account types to support.
4. Decide how you want to create charges.

After making these decisions you can start building your integration. The recipes below and the Connect Quickstart have some examples.

‍