ZenotiHelp

Processor: Adyen direct

ZTZenoti Docs Team Updated August 20, 2026 6 min readGuide

Adyen Direct is an enhanced Adyen integration that separates point-of-sale (POS (Point of Sale)) and e-commerce transactions into distinct merchant accounts and supports a separate payout merchant account. Use Adyen Direct when your organisation needs separate reporting, risk rules, or settlement destinations per channel. If a single merchant account covers all channels, use Processor: Adyen instead.


On this page


Before you begin

Permission: Organization administrator access is required to configure Adyen Direct.

  • You need an active Adyen account with separate POS and e-commerce merchant accounts already provisioned. Zenoti does not create Adyen accounts on your behalf.
  • If you plan to use payout flows, a separate payout merchant account must also be provisioned in Adyen.
  • Identify which centers take in-store payments, which take online payments, and which take both β€” each channel is pointed at a specific merchant account.

Adyen Direct vs standard Adyen

Aspect Standard Adyen Adyen Direct
Merchant accounts Single account for all channels Separate accounts per channel (POS, e-commerce, payout)
Reporting Combined per merchant account Per-channel, per-account
Risk rules Shared across channels Configured independently per channel
Settlement destination One bank account per merchant account Can differ per channel if each account settles to its own bank
Configuration surface in Zenoti One credential set One credential set per channel

Use Adyen Direct only if your Adyen contract actually provides these separate accounts. Configuring Adyen Direct against a single shared account offers no benefit and adds setup complexity.


Adyen Direct capabilities in Zenoti

Capability Supported
Sale (POS terminal) Yes β€” routed to the POS merchant account
Sale (e-commerce / HPP (Hosted Payment Page)) Yes β€” routed to the e-commerce merchant account
Refund Yes
Void Yes (pre-settlement; routed through the refund path)
Pre-authorize and capture Yes
Recurring payments Yes
Stored accounts (global tokenization) Yes β€” cards saved on one account are chargeable on linked accounts
Swipe-to-save Yes
Payout merchant account Yes (optional, separate configuration)
Dispute management Yes
Manual card add No β€” use the terminal or HPP
Account health check No

Network requirements

Adyen Direct has the same network requirements as standard Adyen, but because POS and e-commerce can be on different merchant accounts, verify connectivity for each account separately.

Connection Direction Protocol / Port Notes
Zenoti to Adyen API Outbound from Zenoti (cloud) HTTPS / 443 Managed by Zenoti.
Zenoti to Adyen Terminal API (POS account) Outbound from the center network HTTPS / 443 Required only if the center takes terminal payments.
Adyen terminal to Adyen Outbound from the center network HTTPS / 443 Each terminal must be boarded against the POS merchant account.
Webhook notifications from Adyen Inbound to Zenoti HTTPS / 443 Configure once per merchant account in the Adyen Customer Area.

External-system prerequisites

The merchant's Adyen administrator must complete these tasks before Zenoti configuration.

  1. Provision separate merchant accounts in Adyen: one for POS, one for e-commerce, and optionally one for payouts.
  2. Generate API credentials (API key + client key) per merchant account. Do not reuse a single key across channels β€” that defeats the purpose of Adyen Direct.
  3. Allowlist the Zenoti-served domains on the e-commerce account's client key.
  4. For terminal payments, board each terminal against the POS merchant account's store code.
  5. If settlement destinations differ per channel, confirm bank account details with Adyen Finance Operations.

Configure Adyen Direct

  1. Navigate to Configuration > Payments > Process payments > Payment processor onboarding.

  2. Select Adyen Direct.

  3. Enter credentials for each merchant account type.

    Credential set Source / Owner When required
    POS merchant account (API key, client key, merchant account name) Adyen Customer Area > POS merchant account (Adyen administrator) Any center that takes terminal payments.
    E-commerce merchant account (API key, client key, merchant account name) Adyen Customer Area > E-commerce merchant account (Adyen administrator) Any center that takes online/HPP payments.
    Payout merchant account Adyen Customer Area > Payout merchant account (Adyen administrator) Only if you use Adyen to disburse payouts to staff or vendors.
  4. Select Save.

  5. Select Test to verify each credential set.

Security: Each API key is scoped to a specific merchant account. If you rotate one, the other accounts are unaffected β€” but confirm you have re-entered the new key in the correct channel slot.


Assign accounts to centers and channels

After saving credentials, map centers to the accounts that should serve them.

  1. In the Adyen Direct configuration, select each center.
  2. Choose which merchant account serves its POS channel and which serves its E-commerce channel.
  3. Centers that take only one channel leave the other unassigned.
  4. Save.

At run time, Zenoti routes each transaction to the correct account based on the channel (terminal vs HPP/online).


Refund and void

Refund and void behaviour is identical to standard Adyen, but the refund is processed against the same merchant account as the original sale. You cannot refund a POS transaction from the e-commerce account, or vice versa.

Process a refund or void

  1. Open the invoice in Zenoti.
  2. Select Refund and confirm the amount (full or partial).
  3. Zenoti routes the refund to the merchant account that handled the original sale.
  4. Adyen confirms the outcome asynchronously via webhook.

Dual-perspective behaviour

System What it records
Zenoti Refund line on the invoice; the Adyen PSP reference points to the originating merchant account.
Adyen Refund PSP record on the originating merchant account. For pre-settlement transactions, recorded as a cancel (void). Settlement reports show the refund on the same merchant account where the sale cleared.

Reconciliation

Because Adyen Direct uses multiple merchant accounts, you must reconcile per account, not in aggregate.

Layer Source Match key
Zenoti Collections by Invoices, filtered by the Adyen Direct payment method and by center/channel Invoice number + PSP reference
Adyen (POS account) Adyen Customer Area > Transactions, scoped to the POS merchant account PSP reference
Adyen (e-commerce account) Adyen Customer Area > Transactions, scoped to the e-commerce merchant account PSP reference
Bank Per-account settlement reports in Adyen Customer Area > Finance Merchant reference (carries the Zenoti invoice number)

Recommended cadence: reconcile daily at close, per merchant account. A mismatch between channels usually indicates a center misassigned to the wrong account.


Handle transaction failures

Failure mode Symptom Resolution
Adyen unreachable Timeout in POS or HPP. Check outbound HTTPS from POS / terminal / Zenoti to Adyen. Verify in the Adyen Customer Area whether the transaction was recorded before retrying.
Wrong merchant account assigned Transaction succeeds but appears on the unexpected merchant account's report. Review the center's channel-to-account mapping in Configuration > Payments > Process payments > Payment processor onboarding, then open the Adyen entry and correct it. Re-route future transactions.
API key expired for one channel That channel's transactions fail with an authentication error while the other channel works. Regenerate the key in Adyen and re-enter it in the correct channel slot.
Card declined Terminal or HPP returns a decline. Ask for an alternative payment method. The decline code appears in the Zenoti payment log for finance review.
Amount out of processor range Adyen returns an amount-validation error. Verify per-transaction limits on the specific merchant account; limits can differ across accounts.
Currency mismatch Adyen returns "currency not supported for merchant account". The merchant account must be provisioned for the transaction currency. Add the currency to the account or route the center to an account that supports it.
Global tokenization disabled when expected Token charge on another account fails. Confirm the Adyen contract includes cross-account tokenization and that the accounts are linked in Adyen's Global Tokenization configuration.

Tips

  • Confirm your Adyen contract actually includes separate POS and e-commerce merchant accounts before selecting Adyen Direct β€” if it does not, standard Adyen is simpler and functionally equivalent.
  • When global tokenization is in use, saved cards are portable across linked Adyen merchant accounts. Verify with Adyen which of your accounts are linked.
  • Keep one low-value test card and a test center for post-configuration smoke tests. Run a charge and a refund on each channel after any configuration change.

Was this article helpful?
Your feedback helps us improve our documentation.