Account structure

Adyen organizes payments with a clear two-level model: a Company account at the top and one or more Merchant accounts beneath it. Each merchant is an operational unit with its own payment method eligibility, risk settings, processing, and payouts. This separation is practical: you can keep markets, brands, or channels isolated for reporting and reconciliation, while still managing them under a single company umbrella.

Critically, payment methods are enabled at the merchant level. What shoppers see at checkout depends on what’s enabled for the specific merchant that handles the transaction. Payouts, settlement reports, and operational controls also live at this same level, which keeps accounting predictable as you scale.

How this plugin uses it

• Each Sylius Payment Method is explicitly bound to a single Adyen merchant account.

• What appears in Sylius (e.g., cards, digital wallets, BNPL, and other Adyen methods) depends on what’s enabled for that merchant in Adyen.

• You can run multiple methods pointing to different merchants and assign them per channel in Sylius.

Merchant account binding

In Sylius Admin → Payment methods, create or edit the method (Adyen gateway), provide the required credentials, and set Merchant account to your Adyen merchant account identifier.