Adyen for Platforms - Merchant Onboarding

Configure your Adyen for Platforms connection for boarding merchants through Preczn.

Overview

This guide covers everything you need to onboard merchants through your Adyen for Platforms connection — from configuring your connection credentials to initiating the onboarding process.

FeatureSupported
Merchant Onboarding✅ Yes
Merchant RFI Remediation❌ No
One-Time Merchant Import❌ No
Continuous Merchant Import❌ No

Configuring the Connection

Before you can board merchants to Adyen for Platforms, you must first configure an Adyen for Platforms connection in the Preczn dashboard. This connection provides the credentials Preczn needs to communicate with Adyen's onboarding APIs on your behalf.

You need a separate Preczn connection for each Adyen for Platforms merchant account you operate. For example, if you have three Adyen merchant accounts, you should create three distinct Adyen for Platforms connections in Preczn. This ensures merchants are boarded to the correct Adyen merchant account when you assign them to a connection later.

The following fields are required to configure merchant onboarding. Some fields overlap with payment processing — if you have already configured payments on this connection, only the onboarding-specific fields need to be added.

Connection Details

FieldDescription
NameThe display name for this connection in the Preczn dashboard (3–25 characters). We recommend using a name similar to your Adyen Merchant Account ID so the connection is easy to identify.
Company IDThe root-level Company ID for your Adyen account. This value applies across all merchant accounts under your Adyen company.
Adyen Merchant Account IDThe merchant account ID of the specific Adyen for Platforms account you are connecting to this Preczn Platform connection.

API Keys

Onboarding requires three API keys, each created in the Adyen Customer Area under Developers > API credentials. Navigate to your company account (not the merchant account) to create each key.

Payments API Key

This key authorizes Preczn to manage accounts on your behalf. It can also be used for payment processing if you configure both use cases on the same connection.

  1. Click Create new credential.
  2. Select Payments as the credential type.
  3. Set the type to Web Service User.
  4. Under Permissions, enable the following:
SectionPermission
AccountManagement API - Accounts read
AccountManagement API - Accounts read and write
AccountManagement API - API credentials read and write
AccountManagement API - Payout Account Settings Read
AccountManagement API - Webhooks read
AccountManagement API - Webhooks read and write
AccountManagement API - Payment methods read
UncategorizedMerchant PAL Webservice role
  1. Save the credential and copy the API key.
📘

Shared Key

If you are also using this connection for payment processing, the same Payments API Key is used for both. When creating the key, make sure all of the permissions listed above are enabled to support both use cases.

LEM API Key

The Legal Entity Management (LEM) API key authorizes Preczn to create and manage legal entities for merchant boarding.

  1. Click Create new credential.
  2. Select Platforms as the credential type.
  3. Set the type to LEM user.
  4. Save the credential and copy the API key.

No additional permission configuration is needed for this key.

Balance API Key

The Balance API key authorizes Preczn to manage balance platform operations during the boarding process.

  1. Click Create new credential.
  2. Select Platforms as the credential type.
  3. Set the type to Web Service user.
  4. Under the permission sections, enable the following roles:
SectionPermission
Balance Platform ConfigurationBalance Platform BCL role
TransfersTransferService Webservice Initiate role
UncategorizedPlatform Components: Admin
  1. Save the credential and copy the API key.

Webhook Configuration

Onboarding requires manual webhook configuration so that Adyen can notify Preczn of boarding status changes.

Webhook URL — After saving the connection, Preczn displays a Webhook URL in the connection details. Copy this URL and configure it as the webhook endpoint in your Adyen Customer Area so Adyen can send onboarding notifications to Preczn.

Webhook Signing Secret — When configuring the webhook in the Adyen Customer Area, Adyen generates an HMAC signing secret. Copy this value and enter it into the Webhook Signing Secret field on your Preczn connection. Preczn uses this to verify the authenticity of incoming onboarding-related webhook notifications.

🚧

Onboarding Only

The Webhook Signing Secret and manual webhook configuration are only required for merchant onboarding. For payment processing, Preczn automatically subscribes to payment-related webhooks.

Verify and Save

  1. Click Verify Connection — Preczn validates your credentials against Adyen.
  2. If verification succeeds, click Add Connection to save.
👍

Credential Verification

Preczn verifies your Company ID, Payments API Key, LEM API Key, and Balance API Key during the verification step. If verification fails, double-check that each key was created with the correct credential type and permissions as described above.