PayPal
Org-level connection
PayPal 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.
How to connect
Go to developer.paypal.com → Dashboard → My Apps & Credentials
Create a Live app and copy the Client ID
Paste the Client ID below as the API key
Note: Full OAuth flow coming soon. Use Client ID for now; sandbox and token auth coming.
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for PayPal. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
payments:read | Read payments | Read only |
invoices:read | Read invoices | Read only |
orders:read | Read orders | Read only |
reporting:read | Read transaction reports | Read only |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/paypal to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g., Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
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.
Still stuck? We're happy to help.
Contact support →