Stitchflow
Adyen logo

Adyen SCIM guide

Connector Only

How to automate Adyen user provisioning, and what it actually costs

Summary and recommendation

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.

The strategic alternative

Adyen has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?No
SCIM tier requiredN/A
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0
DocumentationOfficial docs

Supported identity providers

IdPSSOSCIMNotes
OktaNo SCIM available
Microsoft Entra IDNo SCIM available
Google WorkspaceVia third-partyNo native support
OneLoginVia third-partyNo native support

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Adyen accounts manually. Here's what that costs:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The Adyen pricing problem

Adyen gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
Manual managementTransaction fees only
Okta connectorTransaction fees + Okta licensing
Other IdPsTransaction fees only

Provisioning options

MethodCostSCIM SupportSSO Support
Manual managementTransaction fees only❌ None✓ SAML 2.0
Okta connectorTransaction fees + Okta licensing✓ Via Okta only✓ SAML 2.0
Other IdPsTransaction fees only❌ Manual provisioning✓ SAML 2.0

Adyen's transaction-based pricing

Processing fee
€0.10-0.15 per transaction (~$0.13 USD)
Payment method fees vary by method
Interchange++ pricing passes costs directly through
No setup or monthly platform fees

What this means in practice

If you use Okta: You get SCIM provisioning, but your payment platform access depends entirely on Okta's third-party connector. If the connector breaks or Okta deprecates it, your provisioning stops working.

If you use any other IdP: You're stuck with manual user management. Every new hire in payments, finance, or risk analysis requires manual account creation in Adyen's platform.

For a payment processor handling sensitive financial data, this creates significant operational risk around access control.

Additional constraints

Company account requirement
SSO only works with company accounts, not standard merchant accounts
Role prerequisites
Users need Merchant admin or Merchant user management roles for SSO access
Backup admin mandate
Adyen requires maintaining at least one non-SSO admin account for troubleshooting
Legal acceptance
Users must accept legal notices before SSO activation
Compliance sensitivity
Payment platform access requires strict controls that manual provisioning can't reliably provide

Summary of challenges

  • Adyen does not provide native SCIM at any price tier
  • Organizations must rely on third-party tools or manual provisioning
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What Adyen actually offers for identity

SAML SSO (Company Account Required)

Adyen supports SAML 2.0 integration for single sign-on:

SettingDetails
ProtocolSAML 2.0
Supported IdPsOkta, Azure AD, AD FS, custom SAML providers
Account requirementMust have company account (not merchant account)
Role requirementMerchant admin or Merchant user management role
JIT provisioning✓ Yes

Critical setup requirement: You must maintain at least one admin account without SSO enabled for troubleshooting purposes. Legal notice acceptance is also required before enabling SSO.

SCIM Provisioning (Okta Only)

Adyen's user provisioning is limited to Okta integration:

FeatureOkta SupportOther IdPs
Create users✓ Yes❌ No
Update attributes✓ Yes❌ No
Deactivate users✓ Yes❌ No
Group linking✓ Yes❌ No
Schema discovery✓ Yes❌ No

Major limitation: If you use Entra ID, Google Workspace, or OneLogin as your identity provider, there's no automated provisioning available. You're stuck with manual user management for your payment platform access.

Why This Falls Short for Payment Teams

Payment platforms require strict access control for compliance, but Adyen's provisioning limitations create operational headaches:

Okta lock-in
No SCIM support for other enterprise IdPs
Manual processes
Teams using Entra or Google must manually provision payment access
Compliance gaps
Limited automation makes it harder to maintain proper access controls
Complex setup
Requires specific account types and role configurations

For payment operations teams that need reliable, IdP-agnostic provisioning, these constraints translate to ongoing manual work and potential compliance risks.

What IT admins are saying

Community sentiment on Adyen's provisioning setup reveals frustration with complex configuration requirements:

  • Complex setup requirements - Multiple prerequisites including company account setup and specific admin roles
  • Mandatory non-SSO admin maintenance - Must keep at least one admin account outside of SSO for troubleshooting
  • Account type confusion - Requires company account rather than merchant account, creating setup barriers
  • Hidden compliance steps - Legal notice acceptance required before SSO can be activated

Keep one admin without SSO for troubleshooting

Adyen official documentation

Requires Merchant admin or Merchant user management role

Okta integration requirements

The recurring theme

Even when Adyen supports SCIM provisioning through Okta, the setup complexity and mandatory non-SSO admin requirement creates ongoing operational overhead that defeats the purpose of automated user management.

The decision

Your SituationRecommendation
Small payment team (<10 users)Manual management with SSO for authentication
Okta users needing basic provisioningUse native Okta integration for SCIM
Large finance/payment ops team (20+ users)Use Stitchflow: automation essential for sensitive payment access
Multi-IdP environment (Entra, Google Workspace)Use Stitchflow: no native SCIM outside Okta
Enterprise with strict compliance requirementsUse Stitchflow: automation essential for audit trail and access control

The bottom line

Adyen offers SCIM provisioning through Okta but leaves other IdP users managing payment platform access manually. For payment teams using Entra, Google Workspace, or needing consistent automation across multiple platforms, Stitchflow eliminates the manual overhead while maintaining the strict access controls that payment compliance requires.

Make Adyen workflows AI-native

Adyen has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.

Covers apps without native SCIM, including the ones without APIs
Less than a week, start to finish (~2 hours of your time)
Built with your team; extend to anything else in the company
Book a Demo

Technical specifications

SCIM Version

Not specified

Supported Operations

Not specified

Supported Attributes

Not specified

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • Requires company account (not merchant account)
  • Requires Merchant admin or Merchant user management role
  • Keep one admin without SSO for troubleshooting
  • Legal notice acceptance required for SSO

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Okta Admin Console → Applications → Adyen → Sign On

Enterprise required for SCIM

Use Stitchflow for automated provisioning.

Unlock SCIM for
Adyen

Adyen has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.

See how it works
Admin Console
Directory
Applications
Adyen logo
Adyen
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

PayPal logo

PayPal

SCIM Tax

Payments / Fintech

SCIM StatusIncluded
Manual Cost$6,534/yr

PayPal supports SCIM through its Braintree platform, but only on Enterprise accounts with transaction-based pricing starting at 2.59% + $0.49 per transaction. The bigger issue: SCIM onboarding is irreversible—once enabled, you can never revert to manual user management in the control panel. You also can't create or delete groups via SCIM (only update existing ones), and all non-SSO users must be converted to SSO before SCIM activation. This creates a significant deployment risk for payment operations teams. The irreversible nature means you're locked into SCIM management permanently, while the group limitations force manual administration for new merchant access patterns. For finance teams managing payment platform access, this inflexibility conflicts with the dynamic nature of payment operations where user roles and merchant account access frequently change.

View full guide
6sense logo

6sense

No SCIM

B2B Revenue Intelligence / ABM

ProvisioningNot Supported
Manual Cost$11,754/yr

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.

View full guide
ActiveCampaign logo

ActiveCampaign

No SCIM

Marketing Automation / Email

ProvisioningNot Supported
Manual Cost$11,754/yr

ActiveCampaign, the marketing automation platform, does not offer native SCIM provisioning on any plan. While the Enterprise plan ($145+/month) includes SAML 2.0 SSO with just-in-time (JIT) provisioning, this only creates user accounts on first login—there's no automated deprovisioning when employees leave or change roles. New SSO users are automatically added to a generic "SSO Users" group with configurable permissions, but IT teams have no way to programmatically manage user lifecycles or enforce granular access controls based on department or role changes. This creates a significant gap for marketing teams that need to manage access to customer data and campaign tools. When employees leave the company or change departments, their ActiveCampaign access must be manually revoked, creating compliance risks and potential data exposure. The lack of automated deprovisioning means former employees could theoretically retain access to sensitive marketing data and customer information until someone manually removes them from the platform.

View full guide