Products
Cell Pulse Cell Defender Cell Shield Integrations
Resources
Security & Trust
Pricing Login
Get a Demo
Setup Guide

Connect Adyen to Cell Payments

Follow these steps to connect your Adyen account. Cell Payments integrates via the Adyen Management API for real-time transaction monitoring and dispute management.

Estimated setup time: 8 minutes

Required Credentials

CredentialTypeWhere to Find
API KeyRequiredAdyen CA → Developers → API Credentials
HMAC KeyRequiredAdyen CA → Developers → Webhooks
Merchant AccountRequiredAdyen CA → Account → Merchant Accounts
1

Log in to the Adyen Customer Area

Go to ca-live.adyen.com and log in with your Adyen credentials.

Make sure you are at the Company level (not a specific merchant account) to create credentials that work across all your merchant accounts.

2

Create a New API Credential

Navigate to Developers → API credentials in the left sidebar.

Click Create new credential and select Web service user as the credential type.

Give the credential a descriptive name like CellPayments_Integration.

3

Set API Permissions

In the credential settings, navigate to the Server settings tab. Under Roles, enable the following:

RolePurpose
Merchant PAL Webservice roleAccess payment data and transaction details
Merchant Recurring roleView recurring payment information
API Disputes roleManage disputes via Cell Defender
Management API - Accounts readRead merchant account configuration
Management API - Webhooks read and writeConfigure webhook notifications

Under Allowed origins, add https://app.cell-payments.com.

4

Generate the API Key

In the same credential page, scroll to the Authentication section.

Click Generate API key. A new API key will be generated and displayed once.

Copy the API key immediately and store it securely.

Click Save changes at the bottom of the page to finalize the credential.

The API key is shown only once. If you navigate away without copying it, you will need to generate a new one.

5

Create a Standard Webhook

Navigate to Developers → Webhooks in the sidebar.

Click + Webhook and select Standard webhook.

Configure the webhook with the following settings:

  • URL: https://app.cell-payments.com/api/webhooks/adyen
  • Method: JSON
  • SSL Version: TLS 1.3 (recommended)
  • Active: Yes
6

Generate the HMAC Key

In the webhook configuration, navigate to the Security section.

Click Generate new HMAC key. Copy the HMAC key value immediately.

The HMAC key is used to verify that webhook notifications are genuinely from Adyen and have not been tampered with.

The HMAC key is required for Cell Payments to validate incoming Adyen webhooks. Do not skip this step.

7

Select Webhook Events

Under Events, select All events to ensure Cell Payments receives complete data, or at minimum select:

  • AUTHORISATION — Payment authorization events
  • CAPTURE — Payment capture events
  • CANCELLATION — Cancellation events
  • REFUND — Refund events
  • CHARGEBACK — Chargeback notifications
  • CHARGEBACK_REVERSED — Chargeback reversals
  • NOTIFICATION_OF_CHARGEBACK — Pre-chargeback notifications
  • SECOND_CHARGEBACK — Pre-arbitration chargebacks
  • REQUEST_FOR_INFORMATION — Retrieval requests

Under Additional settings, check all available options for maximum data. Click Save configuration.

8

Copy Your Merchant Account Code

Navigate to Account → Merchant accounts in the Customer Area.

Copy the Merchant account code for the account you want to connect. It typically looks like YourCompanyECOM or YourCompanyPOS.

If you have multiple merchant accounts, you can connect each one separately in Cell Payments.

9

Paste in Cell Payments

Log in to your Cell Payments account at app.cell-payments.com.

Navigate to Settings → Connections and select Adyen from the list of available processors.

Paste your credentials:

  1. Enter your API Key
  2. Enter your HMAC Key
  3. Enter your Merchant Account code

Click Connect. Cell Payments will validate the credentials and begin syncing your Adyen data.

Initial data sync may take 5-10 minutes depending on your transaction volume. Historical data will populate progressively.