Adyen for Platforms - Merchant Onboarding

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.

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

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.

📘

Onboarding Permissions Only

The API key permissions listed below are the minimum required for merchant onboarding through Preczn. If you are also using Preczn for payment processing and tokenization, additional permissions will be required. Refer to the relevant integration guides for those permission requirements.

⚠️

Missing Permissions in Adyen Customer Area?

Some of the permissions listed below may not be visible in your Adyen Customer Area by default. If you are unable to locate a required permission or role, contact Adyen Support to request access. This is a common configuration step when setting up Adyen for Platforms integrations.

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:

5. 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:

5. 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.

Boarding a Merchant

Once your connection is configured, you can begin boarding merchants to your Adyen for Platforms account through Preczn.

Assign a Platform Connection

Before boarding can begin, each merchant must be assigned to the correct Adyen for Platforms connection. Because each Adyen for Platforms merchant account is configured as a separate connection in Preczn, the selected connection determines which Adyen merchant account the merchant will be boarded to.

🚧

Required Before Boarding

A merchant cannot be boarded until a Platform Connection ID is assigned.

Via the Dashboard

1. Navigate to the merchant's profile in the Preczn dashboard. You'll want to click the Adyen for Platforms icon on the merchant connections.
2. Select the appropriate Adyen for Platforms connection from the Platform Connection dropdown.
3. Save the merchant profile.

Via the API

For integrators managing merchants at scale, you can assign platform connections programmatically using the Preczn API. This is useful for bulk-updating existing merchants or automatically assigning connections as new merchants are created.

Step 1: List available platform connections

Retrieve the Adyen for Platforms connections configured on your platform.

GET /v1/merchants/{merchantId}/connections/AdyenForPlatforms/available-platform-connections

Response:

[
  {
    "id": "pfmCon_abc123",
    "name": "US Operations",
    "companyId": "Preczn",
    "processorMid": "PrecznECOM"
  }
]

Use the id value from the desired connection as the platformConnectionId in the next step.

Step 2: Update a merchant with the platform connection

Assign the connection to an existing merchant's Adyen for Platforms processor.

PATCH /v1/merchants/{merchantId}/connections/AdyenForPlatforms

Request body:

{
  "platformConnectionId": "pfmCon_abc123"
}

📘

Bulk Operations

To assign a platform connection to multiple existing merchants, loop through your merchant list and issue a PATCH request for each one. For new merchants, create the merchant first via POST /v1/merchants, then assign the platform connection with the PATCH endpoint above.

Submit via Boarding Forms

Merchants must be boarded using Preczn Boarding Forms. This is required because the Adyen terms of service are dynamically generated as part of the boarding form flow.

Once a merchant has been assigned a platform connection, direct them to complete the boarding form. The form collects the required merchant data and presents the Adyen terms of service for acceptance. Upon submission, Preczn transmits the merchant data to Adyen for underwriting.

For details on creating and configuring boarding forms, see:

• Boarding Forms — Overview and setup
• Creating Forms — Step-by-step form creation
• Boarding Form Templates — Configuring form templates

🚧

Boarding Forms Required

Merchants cannot be boarded to Adyen for Platforms via the API alone. The boarding form is necessary to generate and present the Adyen terms of service, which the merchant must accept before boarding can proceed.

Enabling PCI Compliance in Boarding Forms

When creating a boarding form via the API for an Adyen for Platforms merchant, you can include the displayPciSaq field to display the PCI Compliance step in the onboarding form. This step embeds the required SAQ (Self-Assessment Questionnaire) compliance agreement that the merchant must complete during the boarding process in order to successfully process ecommerce payments with Adyen.

To enable the PCI Compliance step, set displayPciSaq to true in your form creation request:

POST /v1/merchants/{merchantId}/forms

{
  "displayPciSaq": true,
  "displayTos": true
}

📘

Note

displayPciSaq can only be enabled during form creation via the API at this time. Support for enabling this option in Form Templates and the Dashboard will be added in future releases.

⚠️

Important

Without the PCI Compliance step enabled, merchants boarding through Adyen for Platforms will not be able to process ecommerce payments. Ensure displayPciSaq is set to true for any merchant that needs to accept card-not-present transactions.