Skip to main content
Ensure you have access to your Stripe Dashboard with appropriate permissions to view API keys.

​
Choosing Your Environment

Stripe provides separate API keys for live (production) and test environments. Choose the appropriate environment based on your use case.

1

Select the Right Environment

When connecting Stripe to StackOne, you’ll be asked to select an environment.

  • Production - Use for real transactions with actual customer data and charges
  • Test Mode - Use for development and testing without processing real payments
  • Test Mode uses simulated data and test card numbers
  • You can switch environments later by creating a new connection

​
Accessing Your API Keys

Stripe automatically generates API keys for your account. You’ll need to copy your Secret key to connect with StackOne.

1

Sign in to Stripe

Sign in to your Stripe account.

2

Switch to Test Mode (if needed)

To access test keys, you must first enable Test mode in the dashboard.

  • Look for the Test mode toggle in the top-right corner of the dashboard
  • Click the toggle to switch between Live and Test mode
  • When Test mode is enabled, you’ll see an orange TEST MODE banner at the top
  • The dashboard URL will change to include /test (e.g., dashboard.stripe.com/test/apikeys)
3

Navigate to API Keys

Go to Developers > API keys in the left sidebar.

4

Reveal and Copy Your Secret Key

Locate your Secret key and copy it for use in StackOne.

  • Find the Secret key row in the Standard keys section
  • Click Reveal test key or Reveal live key to show the full key
  • Click the copy icon or select and copy the key
  • Test keys start with sk_test_ and live keys start with sk_live_
  • Store your Secret key securely as it provides full API access to your Stripe account

​
Matching Your Key to Your Environment

Ensure your API key matches the environment you selected in StackOne.

1

Verify Key and Environment Match

Use the correct key type for your selected environment.

  • If you selected Production environment, use a key starting with sk_live_ or rk_live_
  • If you selected Test Mode environment, use a key starting with sk_test_ or rk_test_
  • Using mismatched keys and environments will cause authentication errors

​
Using Restricted API Keys (Optional)

Instead of a secret key with full access, you can use a restricted API key to limit permissions to only the resources StackOne needs.

1

Create a Restricted Key

Restricted API keys are drop-in replacements for secret keys and work with the same Bearer token authentication.

  • In Developers > API keys, click Create restricted key
  • Under How will you be using this key?, select the option that best matches your use case (Powering an integration you built, Providing this key to a third-party application, Authorising an AI agent)
  • Give the key a descriptive name (e.g., “StackOne Integration”)
  • At minimum, grant Read permission for Customers to pass the connection test
  • Grant Read or Write permissions for any additional resources you want StackOne to access
  • Click Create key and copy the generated key
  • Restricted keys start with rk_live_ (production) or rk_test_ (test mode)
  • Some actions may fail if the restricted key does not have the required permissions for that resource

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • API Key
3

Connect

  • Click Connect
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.