Introducing /v2/accounts: A new, unified identity for Stripe's platform users

Stripe Connect
1

Calling all Connect developers! We’re launching our new /v2/accounts API that combines /v1/customer and /v1/accounts into a single object. We’re looking for people to help us test our new API starting early December. By signing up you’ll:

  • Get first access to the next generation of Stripe APIs
  • Combine your user representations into one easily-manageable object
  • Influence our API shape with your feedback

Read on to learn more and sign up here!

Our v1 APIs

In our current v1 abstractions, a platform’s user is often represented differently across the Stripe products the platform uses. For example:

  • An Account object to facilitate payment processing
  • A separate Customer object to collect payments for Subscriptions

But we heard from our Connect developers that maintaining these representations to improve their users’ experiences can be challenging. Platform developers want to easily know every way a person or company is using the platform, so they can help those users grow their businesses.

Introducing /v2/accounts

With /v2/accounts, we’re addressing these limitations head-on. Here’s what’s changing:

  1. A unified representation: A single Account object that works across all Stripe products
  2. Centralized identity data: User information is collected in a single place to leverage wherever their Account is used
  3. One account, multiple configurations: Easily enable new functionality to users within that same Account object

Before
Before708×336 12 KB

After
After1046×572 20.1 KB

Example: A single identity, a single v2 Account

Here’s a quick example of how you can create a v2 Account with both Customer and Merchant configurations:

Unified identity: /v2/accounts (may not be the final API shape) 
POST /v2/accounts

{
  include: ["configuration.merchant", "configuration.customer"],
  display_name: "Sally's T-Shirts", 
  contact_email: "sally@sallysshirts.com", 
  identity: {
    type: "company",
    country: "US",
    business_entity: {
      name: "Sally Anderson T-Shirt Company",
      doing_business_as: "Sallys T-Shirts"
    }
  },
  configuration: {
    customer: {
      shipping: {
        name: "Sally's T-Shirts",
        address: {
          line1: "12345 Main Ave",
          line2: "Unit 3",
          city: "Springfield",
          state: "CA",
          zip: "123456",
          country: "US"
        }
      }
    },
    merchant: { 
      mcc: "5734",
      support: {
        email: "help@sallysshirts.com",
        phone: "123-456-7891",
        url:"www.sallysshirts.com",
        address: {
          line1: "1234 Main Ave",
          line2: "Unit 3",
          city: "Springfield",
          state: "CA", 
          postal_code: "123456",
          country: "US"
        }
      },
      card_payments: {
        decline_on: {
          avs_failure: true,
          cvc_failure: true
	    }
       },
	  features: {
	    card_payments: {requested: true}
	  }
    }
  }
}

This single API call creates an account that functions as both a customer paying you and a merchant processing their own payments, facilitated by you—something that previously required multiple API calls and objects.

The future of Stripe’s platform APIs

The introduction of /v2/accounts on Stripe Connect is just the beginning. This new foundation will enable Connect developers to:

  1. Simplify integrations: Developers will be able to work with a single, coherent Account object across all Stripe products, starting with Direct Billing and Embedded Payments.
  2. Go to market with new financial products faster: As we expand our configurations, we’ll make it easier than ever for platforms to start using Stripe’s products
  3. Improve their user’s experiences: Platforms will gain an increasingly holistic view of their users across the API and Stripe dashboard, and can provide them a better experience across financial services with ease.

We’re excited to see what developers will build with this new capability. /v2/accounts on Stripe Connect will be launched for SaaS platforms in private preview in early December. Be one of the first to try out our new API and give us feedback: sign up here!

7 Likes
2

hi, I am interested in this
New Account ID - acct_1QEp5cCKSVdOFHTp

2 Likes
3

Would I be able to add other websites like Facebook accounts or you know can I pretty much just use it for anything I can attach it to my square and my Wix website whatever other websites that I have is that a possibility with this new setup or no

2 Likes
4

Hi @planurparty86 ! Could you tell us a little bit more about what you’re trying to do here?

2 Likes
5

@sajjadurrehman1517 thanks for reaching out! Happy to get you set up. Look forward to an email from us.

1 Like
6

Hi there! I would like to learn more - can this help us with Connect + Issuing?

7

Where are the docs for /v2/accounts APIs ?

8

Hey @ash - the docs are here.

9

Very interesting! I cant wait to try this; Im wondering would this make it possible to purchase Connect account subscriptions with platform level customers?

11

We’re rolling out support for Issuing later this year!

12

@keano not sure I understand what you mean by platform-level customers, could you give me an example?

13

Hey @vibhusharma like trying to start a subscription in a connect account product with a customer from the Platform level (https://dashboard.stripe.com/test/customers) customer list, the connect account is not able to locate the customer since Connect and Platform are separate services

Hope this helps explain it a little better,

I would love to test Accounts V2 out anyway, I was having a hard time accepting the v2 invite and attempted to reach out via email but wondering if we can activate it for my current account

acct_1PlBf8FTBqJByBUQ

14

Hey @vibhusharma - when you say that support for issuing will be released later this year, what do you mean by that? Will it be possible for the platform to invoice connected account for the subscription and get the payment from the connected account balance? If so, would the platform incur a fee for doing so?

15