Summary and recommendation
Corpay user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Corpay is a financial operations platform focused on payments, FX, and cross-border transfers.
Its admin and user-management workflows are not publicly documented - the help center requires authentication to access, so operational details cannot be independently verified from public sources.
Like every app in a managed IT portfolio, Corpay requires a verified offboarding path before it can be safely operationalized at scale.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | N/A |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant functionality outside the modules licensed for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their role. | May not be able to manage tenant settings or other users. | Exact privileges can vary by tenant configuration. |
Permission model
- Model type: role-based
- Description: Corpay appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations or service credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared dashboards, configurations, and records remain available unless separately removed. |
| Integrations | Review service credentials and integration ownership separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token and integration review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named user | Administrative or standard access to the tenant. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Public seat-level licensing details are not fully documented.
The cost of manual management
Because no public documentation describes Corpay's permission model, seat types, or offboarding flow, the true operational cost of managing users manually is difficult to quantify. Without a clear deactivate-vs-delete distinction or a documented admin console path, orphaned accounts with payment or FX permissions represent direct financial exposure.
Corpay's financial context makes that risk higher than average compared to most SaaS tools.
The decision
Every app handling payments or FX in your stack demands a confirmed offboarding and permission workflow before it goes into production use - Corpay is no exception.
Teams should open a direct conversation with Corpay's enterprise or support team to resolve whether role-based access control exists, whether deactivation is reversible, and whether any IdP integration is available under a partner agreement. Do not assume capabilities exist or do not exist based on this guide alone.
Bottom line
Corpay's user-management surface is opaque from the outside - its help documentation is gated, community signal is absent, and no SCIM or provisioning API is publicly documented. For a platform handling payments and FX, that opacity carries real access-risk implications.
Until Corpay or a verified admin source confirms the exact offboarding and permission workflow, treat every manual process here as unverified and validate directly with the vendor before operationalizing at scale.
Automate Corpay workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
