Skip to main content
9Pic Checkout is a Beta, Enterprise plan feature. Create Stripe keys only in the Stripe account and mode you intend to use for the event.

Overview

A Stripe restricted key lets 9Pic Checkout use only the Stripe permissions it needs instead of a full-access secret key. Create the key in Stripe first, then paste it into Payment Config -> Add Gateway -> Stripe in 9Pic. Use the downloadable Stripe Restricted API Key Setup Guide as your external checklist while following this dashboard guide.
Stripe Developers API keys page showing the Restricted keys section and Create restricted key button with existing key values redacted

Stripe API keys page

Before You Start

Make sure you have:
Never place restricted keys in a public repository, frontend/mobile app, browser script, email, or chat message. Treat them like passwords.

Create the Restricted Key in Stripe

1

Open API keys

Sign in to Stripe and open Developers -> API keys. In the Restricted keys section, click Create restricted key.
2

Choose the purpose

When Stripe asks how you will use the key, select Powering an integration you built, then click Continue.
Stripe Create a restricted key panel showing the Powering an integration you built option

Choose how the restricted key will be used

1

Choose your own permissions

Select Choose your own so you can grant only the permissions 9Pic Checkout needs.
2

Name the key

Use a clear name such as 9Pic Checkout Restricted Key. If you maintain separate test and live keys, include that in the name.
Stripe Create restricted API key page showing the key name field and the permissions table

Restricted key name and permission table

Required Stripe Permissions

Set only the rows 9Pic needs, and leave unrelated resources on None.
Stripe may rename or combine rows over time. For example, some accounts show Charges and Refunds as one row. If Stripe shows a permission-denied message later, edit the restricted key, add the missing resource permission, save, and test again.
Stripe permissions table showing Charges and Refunds, Customers, Events, and Files rows

Core permissions in Stripe

Stripe permissions table showing Payment Intents, Payment Method Configurations, Payment Method Domains, and Payment Methods rows

Payment permissions in Stripe

Save the Key Safely

1

Review before creating

Confirm the key name, Stripe account, test/live mode, and permissions before you click Create key.
2

Create and copy once

Click Create key. Stripe shows the restricted key value only once. Copy it immediately and store it securely.
3

Do not share it casually

Do not paste the key into email, chat, screenshots, task tickets, public documents, or browser-side code.
Do not create a live key until the Stripe account is ready for real payments. Test the setup with an rk_test_ key first, then create a separate rk_live_ key for production.

Add the Key to 9Pic

1

Open Payment Config

In 9Pic, open Payment Config from the dashboard sidebar.
2

Add a Stripe gateway

Click Add Gateway, choose Stripe, and paste the restricted key into the Stripe Secret Key field. The field stores the protected Stripe credential for your organisation, even when the key starts with rk_test_ or rk_live_.
3

Create the gateway

Click Create Gateway. The gateway list should show the Stripe configuration as Configured.
4

Map events to Stripe

In Event Mapping, assign the Stripe gateway to each event that should use Stripe for 9Pic Checkout.

Verify the Setup

Before using Stripe for a live event:

Troubleshooting

Open the restricted key in Stripe, find the resource named in the error message, set the needed permission, save, and retry the test payment or invoice step.
Create a new restricted key, store it securely, add the new value to 9Pic, then revoke the unused key in Stripe.
No. Keep separate keys for test mode and live mode. This reduces mistakes and makes rotation easier.
Yes. Paste the restricted key value there. Stripe restricted keys start with rk_test_ in test mode and rk_live_ in live mode.

Next Steps

Payment Config

Create and manage organisation-level gateway configurations.

Checkout Setup

Assign a gateway to an event, publish plans, and enable Checkout.