Adding Gaucho Plugins to your Stripe Team
How to grant the Gaucho Plugins support team access to your Stripe account for advanced troubleshooting and configuration.
If you need hands-on troubleshooting support, you can temporarily grant the Gaucho Plugins team access to your Stripe account. This allows our team to inspect your transfer configuration, review webhook events, and make test payments to diagnose issues.
When to grant access#
You should consider granting access when:
- You have followed all steps in the Troubleshooting guide without resolving the issue
- Transfers are failing with errors you cannot diagnose
- You need help verifying your Stripe Connect configuration
- Our support team has requested access during a support ticket
How to add a team member#
Log in to your Stripe account and navigate to Settings > Team.
Click + New member (or Invite member, depending on your Stripe Dashboard version).
Enter our support email address:
support@gauchoplugins.comSet the role to Developer. In Stripe’s current Team UI this is one of the granular built-in roles and is the right level for diagnosing transfers, webhooks, Connect accounts, and API logs without granting payout or account-level write access.
If your account has the older View only role, that’s usually too restrictive for live troubleshooting (we can’t inspect API request logs or rotate test webhook signing secrets). The legacy Read & write / Admin roles grant more than we need; only use them if our support team specifically asks.
Click Send invite. Our team will accept the invitation and begin troubleshooting.
Access levels explained#
Stripe periodically reorganises the team-role taxonomy. As of 2026, the dashboard exposes a small set of built-in granular roles plus optional custom roles on higher-tier accounts. The roles we care about for Split Pay troubleshooting are:
| Role | Can View | Can Modify | Recommended for Split Pay support? |
|---|---|---|---|
| Developer | API keys, webhooks, transfers, payments, Connect accounts, API request logs | Test-mode data, webhook endpoints, restricted API keys | Yes — default recommendation. Smallest role that lets us reproduce live issues. |
| Analyst / View only | Payments, transfers, reports (no API keys / no Connect details on legacy View only) | Nothing | Only useful if you want a strictly read-only audit pass. |
| Connect Admin | Everything Developer sees, plus full Connect account management | Connected accounts, Connect settings | Use if our support team specifically asks because the issue is Connect-onboarding-related. |
| Administrator / Owner | Everything | Everything (including bank accounts and team membership) | Not recommended. Stripe also reserves Owner for the original account creator — you can’t hand that out anyway. |
| Custom role | Whatever permissions you assemble | Whatever permissions you assemble | If your org uses custom roles, build one that mirrors Developer’s permissions and assign that. |
If you don’t see one of these labels, it’s likely been renamed or replaced under your Stripe account’s current role set. The Stripe Roles reference always reflects the current naming.
Revoking access#
Once troubleshooting is complete, you can remove our team member at any time:
- Go to Settings > Team in your Stripe Dashboard
- Find
support@gauchoplugins.comin the team member list - Click the three-dot menu and select Remove
We recommend revoking access after your support case has been resolved. While Developer access is limited, it is good security practice to remove team members who no longer need access.