PayPal SCIM guide

Adyen offers SCIM 2.0 provisioning, but only through Okta's integration—there's no native SCIM endpoint. This creates a significant vendor lock-in scenario where your provisioning capabilities are entirely dependent on using Okta as your identity provider. Teams using Azure Entra, Google Workspace, or OneLogin are left with manual user management despite Adyen supporting SAML SSO with these platforms. The Okta integration itself requires maintaining a company account (not just a merchant account) and keeping at least one non-SSO admin for troubleshooting, adding operational complexity. For payment platforms handling sensitive financial data, this provisioning gap creates serious compliance risks. Your finance team, payment operations staff, and developers need timely access to process transactions and manage risk controls, but without automated provisioning, you're stuck with manual onboarding that can delay critical payment operations. The requirement to maintain non-SSO admin accounts also creates a security backdoor that compliance auditors will flag.

Box offers automated user provisioning through IdP integrations with Okta and Microsoft Entra ID, but this is not SCIM-compliant provisioning. Instead, Box uses a proprietary API that violates core SCIM standards—the userName attribute isn't required, error codes are non-standard, and attribute mapping is Box-specific. This creates a misleading situation where Box appears to support modern provisioning but actually locks you into IdP-specific integrations. Provisioning requires Business plans ($15/user/month) or higher, and only works with major IdP vendors. This proprietary approach creates significant challenges for IT teams managing multi-vendor environments or planning IdP migrations. Since Box's provisioning relies on custom integrations rather than standardized SCIM, switching identity providers means rebuilding provisioning workflows from scratch. Organizations using less common IdPs, those requiring SCIM compliance for audit purposes, or teams running mixed identity environments are left with manual user management—creating security gaps and administrative overhead that scales poorly as teams grow.

Freshdesk supports SCIM provisioning, but only on the Enterprise plan at $79/agent/month. This creates a significant cost barrier for smaller support teams who need automated provisioning but can't justify nearly $1,000/year per agent just to access SCIM. The provisioning system distinguishes between agents (who handle tickets) and contacts (end users), requiring careful configuration to ensure the right people get the right access levels. Role mapping can also require additional setup work to properly assign support agents to appropriate permission groups. For customer support teams, this pricing gate is particularly problematic because support agents often have high turnover rates and need immediate access to handle incoming tickets. Manual provisioning delays mean either security gaps (shared accounts) or customer service delays (agents waiting for access). The Enterprise plan requirement forces smaller teams to either accept manual processes or overpay for features they may not need.