Adyen Integration

Adyen Integration

Scimify provisions Adyen Customer Area users from your identity provider (IdP), including optional role and account access assignments.

Capabilities

• User provisioning — create, update, and deactivate Adyen Customer Area users from your IdP
• User-only — group provisioning is not supported
• Company or merchant scope — each Scimify instance targets either a company account or a single merchant account
• Test or live — use separate instances for test and live (separate Adyen credentials per environment)
• Optional access control via SCIM — assign Adyen roles, merchant accounts (company instances), and account groups
• Deprovisioning — unassign or deactivate in your IdP disables the Adyen user (users are not permanently deleted)

Not supported: Partner users must be managed in the Adyen Customer Area.

Prerequisites

• Permission to manage users in your Adyen company or merchant account
• An Adyen API key with Management API—Users read and write (API credentials, API key roles)
• Your company account ID or merchant account ID
• An IdP or IGA ready for SCIM (see SCIM Configuration)

Use a company instance when you need to grant access across multiple merchant accounts. Use a merchant instance when credentials or access should stay limited to one merchant.

Helpful Adyen background: account structure and user roles.

Configuration Steps

1. Create an Adyen API credential

1. Sign in to the Adyen Customer Area for the correct environment (test or live)
2. Open Developers → API credentials
3. Create or select a credential with Management API—Users read and write
4. Generate the API key and store it securely
5. Note the company or merchant account ID you will connect

Use a dedicated credential for Scimify so you can rotate it independently. Test and live use separate Customer Area environments and API keys.

2. Configure the integration in Scimify

1. Open Integrations in your Scimify admin console
2. Create a new Adyen instance
3. Set a clear display name (for example, Adyen Company Live or Adyen Merchant Test)
4. Choose Account Type: Company or Merchant
5. Enter the matching Account ID
6. Choose Environment: Test or Live
7. Enter the API Key
8. Save, then use Test connection
9. Enable the instance and copy the Scimify SCIM endpoint and API key for your IdP

Create separate instances when you need both test and live, or both company and merchant scopes.

3. Configure SCIM in your IdP or IGA

Follow SCIM Configuration to connect Okta or Lumos to your Adyen instance, then assign users.

Required profile fields for new users:

• Email (used as the Adyen username)
• First name and last name

4. Configure optional custom attributes

To manage roles and account access from your IdP, add the attributes below to your SCIM app profile and map them on create and update.

Custom SCIM attributes

All custom attributes use:

urn:ietf:params:scim:schemas:extension:custom:2.0:User

Attribute: adyen_roles

Setting	Value
Type	String (multi-valued)
External namespace	urn:ietf:params:scim:schemas:extension:custom:2.0:User
Attribute name	adyen_roles
Description	Adyen Customer Area roles for the user

Use exact Adyen role names (for example Merchant standard role, Merchant admin). See User roles. Adyen only allows assigning roles that the API credential’s operator already holds.

Attribute: adyen_merchant_accounts

Setting	Value
Type	String (multi-valued)
External namespace	urn:ietf:params:scim:schemas:extension:custom:2.0:User
Attribute name	adyen_merchant_accounts
Description	Merchant accounts the user can access

Company instances only. On merchant instances this attribute has no effect (the user is already limited to that merchant).

Attribute: adyen_account_groups

Setting	Value
Type	String (multi-valued)
External namespace	urn:ietf:params:scim:schemas:extension:custom:2.0:User
Attribute name	adyen_account_groups
Description	Adyen account groups associated with the user

See Account groups.

Suggested Okta profile attributes

Display name	External name	Type
Adyen roles	adyen_roles	string array (or string)
Adyen merchant accounts	adyen_merchant_accounts	string array (or string)
Adyen account groups	adyen_account_groups	string array (or string)

Set External namespace to urn:ietf:params:scim:schemas:extension:custom:2.0:User for each attribute, then map them in the Okta provisioning profile.

Mapping tips

• Prefer a company instance when users need access to multiple merchants
• Keep role values identical to names shown in Adyen Customer Area
• Drive roles and merchant access from IdP groups or entitlements where possible

What customers should expect

Action in IdP	Result in Adyen
Assign user	Creates a Customer Area user (or updates if they already exist for that account)
Update profile / custom attributes	Updates name, email, roles, and account access as mapped
Unassign or deactivate	Disables the Adyen user

Notes:

• Email is the Adyen username; changing username independently is not supported
• First and last name are required when creating users
• Test and live credentials are not interchangeable

Troubleshooting

Issue	What to check
Connection / authentication failed	API key and Environment (test vs live) match the Customer Area where the key was created
Access forbidden	Credential includes Management API—Users read and write
Account not found	Account Type and Account ID match (company vs merchant)
User create fails	Email, first name, and last name are present on the SCIM profile
Roles not applied	Role names match Adyen exactly; the credential can assign those roles
Merchant accounts not applied	Instance Account Type is Company

Related links

• Adyen account structure
• Adyen user roles
• Adyen API credentials
• Partner users (not supported in Scimify)

Need Help?

Contact support@veraproof.io.