Stripe
API keyPayments & FinanceOrg connection
Org-level connection
Stripe is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
In the Stripe Dashboard, go to Developers → API keys
Click "Create restricted key" and enable the read permissions you need
Copy the restricted key (starts with rk_live_ for production)
Paste it below
Ready to connect?
Sign in to On Belay and open the Integrations page to add Stripe.
Permissions (scopes)
These are the data scopes On Belay can be granted for Stripe. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
charges:read | Read charges | Read only |
customers:read | Read customers | Read only |
payments:read | Read payments | Read only |
refunds:read | Read refunds | Read only |
reports:read | Read reports | Read only |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
The key expires or stops working
Some API keys have expiration policies. Generate a new key in Stripe and update it in On Belay → Integrations → Stripe → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →