Some EAS integrations read sales data directly from your Stripe account. Rather than sharing a full secret key, Stripe lets you issue a restricted key that grants only the permissions the integration needs. This guide explains how to create one.
Before you start: the connection mode must match the key type. A rk_test_... key cannot be used in live mode, and a rk_live_... key cannot be used in test mode.
Creating the restricted key
- Sign in to the Stripe Dashboard.
- Select the required mode:
-
Test mode if you need a key in the format
rk_test_... -
Live mode if you need a key in the format
rk_live_...
-
Test mode if you need a key in the format
- Open Developers and then API keys.
- In the Restricted keys section, click Create restricted key.
- Enter a key name, for example
Remote read-only integration. - Set the minimum required permissions shown in the table below. Leave every other permission set to None.
Resource Permission Account / Connected account Read Checkout Sessions Read Payment Intents Read Charges Read Products Read Prices / Plans Read Tax Rates Read Shipping Rates Read Payment Links, if sales are created through Payment Links or Checkout Read - Click Create key.
- Stripe may ask for a verification code sent by email or SMS. Enter the code to continue.
- Copy the generated key. It should start with
rk_test_...in test mode, orrk_live_...in live mode. - Store the key securely. In live mode, Stripe may show the key only once.
Important: do not grant any Write permissions. This integration requires read-only access only.
Need help?
If you are unsure which permissions to select, or the key is not accepted, contact us at support@easproject.com.