twosided
  • Welcome
  • API Reference
    • Track a new charge
    • Create a new supplier
    • Create a new customer
  • Setting up your Stripe API key
  • Connecting to Sharetribe
Powered by GitBook
On this page

Setting up your Stripe API key

PreviousCreate a new customerNextConnecting to Sharetribe

Last updated 9 months ago

The twosided platform requires a Stripe Secret API key in order to fully operate. You can use the Stripe integration using the account connection only, however you will have to deal with missing data:

  • No personal data of suppliers and customers (only placeholders & customer IDs)

  • Multi-split payments can't be supported

  • No insights into aggregate supplier and customer locations

As this makes the twosided integration less effective, we recommend supplying an API key, or alternatively looking into substituting this information through our .

Setting up a restricted key

Stripe allows you to set up a restricted key in their .

It can be a good option to give looser restrictions to this key, to avoid breaking any integration when the twosided platform updates. At a high-level, we require the following permissions:

  • All core resources – Read

  • All core resources (Connect permissions) – Read

  • All Connect resources – Read

You can restrict the key further to only allow for required resources to be accessible. However, note that this can lead to issues with platform updates later on.

All required resources (Detailed, Latest)
  • Balance transaction sources (Permissions & Connect Permissions) – Read

  • Balance Transfers (Permissions & Connect Permissions) – Read

  • Charges (Permissions & Connect Permissions) – Read

  • Customers (Permissions & Connect Permissions) – Read

  • PaymentIntents (Permissions & Connect Permissions) – Read

  • Products (Permissions & Connect Permissions) – Read

  • All Connect resources – Read

REST API
developer section