# Stripe setup for PopMCP

You end up with one Stripe server-side key, either a restricted key (rk_live_...) or a secret key (sk_live_...), that you paste into PopMCP's "Secret API key" field.

- Auth: API credentials
- Setup time: 5 min
- API base URL: https://api.stripe.com/v1
- Credentials screen: https://dashboard.stripe.com/apikeys
- Provider docs: https://docs.stripe.com/api

## Before you begin

- A Stripe account with the Developer or Administrator role. View-only users cannot create keys
- Two-factor authentication on your Stripe user. Stripe emails or texts a verification code before it will mint a key
- A live-mode account if you want real data. Sandbox keys only ever see test objects

## Get your credentials

### 1. Open the API keys page in live mode

Click Developers at the bottom of the left sidebar, then API keys. Check the mode switch in the top bar and set it to live mode.

Screen: https://dashboard.stripe.com/apikeys

### 2. Create a restricted key with the permissions PopMCP needs

Click Create restricted key and type `PopMCP` into Key name. Set each resource to Read or Write, then click Create key.

Screen: https://dashboard.stripe.com/apikeys/create

### 3. Verify, then copy the key value

Enter the verification code Stripe emails or texts you, then click Continue. Click the key value to copy it, then click Done.

### 4. Paste the key into PopMCP

Open the Stripe connector in PopMCP, paste the key into Secret API key, and save.

## Fields PopMCP asks for

- Secret API key (apiKey) [required]: Stripe Dashboard → Developers → API keys. Use a Secret key (sk_…) for full access, or a Restricted key (rk_…) to limit scope. Stored encrypted; used server-side only. The connection is locked to this key's account.

## Verify

The Stripe connector in PopMCP shows Connected with your account name. Asking for recent payments or your balance returns figures that match the Stripe Dashboard.

## Troubleshooting

### 401 "Invalid API Key provided"

Cause: The key was expired or rotated in Stripe, or you pasted a publishable key (pk_...), which cannot make server-side calls.

Fix: Use a key beginning rk_ or sk_. Mint a fresh one on the API keys page and reconnect.

### 403 "This API key does not have the required permissions"

Cause: A restricted key with that resource set to None or Read.

Fix: On the API keys page open the key's overflow menu, choose Edit key, raise that resource to Write, and save. There is no need to re-copy the key.

### Every query comes back empty

Cause: You copied a sandbox key (rk_test_ or sk_test_). Test mode has its own separate objects.

Fix: Switch the Dashboard to live mode, create the key there, and reconnect.

### Requests are blocked from PopMCP's servers

Cause: An access policy restricting the key to specific IPs, ASNs or countries.

Fix: On the API keys page, open the key's overflow menu, choose Manage access policy, and set it to None or widen the policy.

### You closed the dialog before copying

Cause: Stripe shows a self-created live key only once.

Fix: Open the key's overflow menu, choose Rotate key, pick an expiry, and copy the replacement value. Both keys keep working for up to 7 days.

---

Source: https://www.docs.popmcp.com/docs/integrations/stripe/