Services and business-model fit
Sections ↑Adyen provides payment acceptance and financial infrastructure for enterprises, including financial-services firms. Its finance offering brings account funding, investment withdrawals, currency exchange and outward payments into a common operating environment. For a broker, the relevant work concerns moving and reconciling customer money around the trading service. Adyen’s product description addresses those payment flows; the precise eligible business model matters before a particular integration can be used.[1]
Securities and trading eligibility
| Business covered by the policy | Direct merchant | Platform / partner business |
|---|---|---|
| CFDs, financial spread betting and forex currency options | Restricted | ProhibitedSource 2 |
| Securities brokers and investments in currencies, derivatives, shares or other financial instruments | Restricted | ProhibitedSource 2 |
| Cryptocurrency exchanges | Restricted | ProhibitedSource 2 |
Adyen Uplift adds automated decisions across payment-method presentation, tokenization, fraud controls, authentication and routing. The current module names are Personalize, Tokenize, Protect, Authenticate and Optimize. Adyen describes an engine balancing conversion, fraud and payment cost against business priorities, with dashboards and experiments to examine the effects. Those are payment-processing and checkout functions, rather than a broker’s trading-risk engine.[3]
The Payouts and Payments service can use funds acquired by Adyen or transferred in externally. Disbursements may relate to an incoming payment or be standalone transfers to third-party beneficiaries. Supported destinations include bank accounts and Mastercard or Visa cards, with availability dependent on the destination and route. This outward-transfer service is distinct from paying a merchant its own net acquiring proceeds.[6]
Integration and operating controls
Sections ↑Payment integration choices
| Option | Customer experience | Merchant implementation |
|---|---|---|
| Hosted Checkout | Redirect to an Adyen-hosted payment page. | Build a payment server and a webhook receiver.Source 4 |
| Drop-in | Embed Adyen’s prebuilt payment interface on the merchant’s website. | Build the same server components and initialise the interface locally.Source 4 |
| Sessions flow | Client libraries handle the payment flow from session data. | One Checkout API /sessions request is the standard starting point.Source 5 |
| Advanced flow | More control over supported payment use cases. | Separate /paymentMethods, /payments and /payments/details requests.Source 5 |
Card-data exposure changes the compliance work. Adyen’s encrypted-cardholder-data role for Drop-in, Components and Custom Card fields requires an SAQ A assessment. Sending raw card details through the API requires the API PCI Payments role, an SAQ D assessment and support enablement. Choosing an interface therefore determines more than the appearance of the deposit page.[12]
Access and request controls
| Control | Documented behaviour | Operational consequence |
|---|---|---|
| Credential scope | Roles and selected company or merchant accounts restrict an API identity. Optional IP ranges limit request origins. | Payment, refund and other operational permissions can be separated.Source 10 |
| Key rotation | A new API key activates immediately; its predecessor normally remains valid for 24 hours and can be expired earlier. | Deactivation immediately stops requests; the credential is retained rather than deleted.Source 10 |
| Request duplication | POST idempotency keys last 7–14 days from first submission at company-account level. | The same key is not checked against other regional endpoints; regional failover needs separate duplication controls.Source 9 |
| Employee access | Customer Area supports roles, SAML 2.0 single sign-on and authenticator-app or SMS multifactor authentication. | Separate staff permissions from API credentials; SSO can remove a departing employee’s access.Source 11 |
Payment webhook handling is asynchronous. The documented sequence verifies authenticity, stores the event, acknowledges it with a successful HTTP response such as 200 or 202 within ten seconds, and then runs business logic. Adyen requires integrity verification and describes HMAC validation. Missing acknowledgements trigger retries. Duplicate events can occur; timestamps and, where supplied, sequence numbers matter when updating a ledger. An immediate browser return is therefore only one input into the payment workflow.[8]
Fees, settlement and retained balances
Sections ↑Adyen publishes a fixed processing charge plus a payment-method charge. Other products are priced separately. Its pricing FAQ states that setup, integration, monthly and closure fees are absent, but a minimum invoice can apply according to the industry or business model. That minimum is discussed with sales, so the public payment-method formula is not a complete commercial offer for a financial-services firm.[13]
Published fee structure and settlement conditions
| Item | Published basis | Scope |
|---|---|---|
| Visa example on the UK website | GBP 0.11 processing plus 0.60% and variable interchange/scheme charges. | An illustrative public rate under the Interchange++ model.Source 14Source 15 |
| Processing fee | Charged for submitted transactions even without successful authorisation or capture. | Distinct from settled-payment fees.Source 16 |
| Reconciliation of charges | Processing appears against Received and SentForRefund; acquiring and method fees against Settled. | Invoice adjustments can include risk-refused or externally acquired transactions.Source 15 |
| Accelerated Sales Day Payout | An agreed percentage of captured volume, invoiced monthly. | Approved shorter business-day schedules; may increase the required deposit.Source 17 |
Merchant payouts are net of refunds, chargebacks, fees and adjustments. Like-for-like settlement avoids conversion only where the payment method, acquiring connection and settlement currency support it. Sales Day Payout groups a sales day independently of when the scheme funds Adyen; pass-through follows receipt of those funds. The latter is the only model documented for Africa, Brazil and India. Bank processing and holidays affect arrival after Adyen initiates a payout.[7]
Sales Day Payout requires approval for the relevant sub-account, region, method and currency. Its clock uses the configured transaction day and an agreed business-day payout date. Earlier payout does not remove settlement risk: scheme or acquirer default, or non-receipt 30 days after the transaction day, can require the merchant to repay advanced funds. Unsupported methods remain on pass-through settlement.[17]
The risk Deposit is separate from the optional operating Reserve used to fund refunds and other expenses. Adyen recalculates required deposit coverage daily using processing and reversal exposure. The documented EUR 10,000 threshold is a trigger: when exposure exceeds coverage by more than that amount, Adyen withholds the full shortfall, not just the excess above EUR 10,000. Released excess is added to a subsequent payout.[18][21]
The current merchant terms generally cover agreements entered from 1 November 2023. Fees exclude taxes. Monthly invoices default to EUR unless agreed otherwise; a remaining balance is adjusted against settlement or, without a next settlement, payable or credited within 30 days of the invoice date.[16]
Onboarding, migration and data lifecycle
Sections ↑A free test account supports simulated payments and integration work, but does not confer live acceptance. Adyen’s sequence includes business review, an approved application, a signed contract and the applicable card-data security attestation before access to the live Customer Area. The documentation advises establishing commercial fit before completing the whole integration.[19]
The live application examines the service presented to customers as well as the entity. Website or app information must identify the business, explain payments, refunds and cancellation, disclose privacy practices and provide contact details. Ownership and control evidence can be requested. These checks connect the technical payment journey with the business and counterparties actually being underwritten.[20]
From test account to continuing operations
| Stage | Required work | Why it matters |
|---|---|---|
| Live configuration | Configure live methods, payout accounts, risk settings, API credentials, endpoints and webhooks; test settings are not automatically copied. | Complete PCI requirements and applicable 3D Secure/SCA setup before accepting live payments.Source 21 |
| Incoming payment-data migration | Map shopper references, arrange encrypted files and support tokenization at both providers during the transition. | Adyen charges no migration fee and says migrations usually take ten days or more; this is not a completion commitment.Source 22 |
| Moving stored payment details onward | Use enabled Checkout API forwarding to a PCI-compliant third party, with required roles and matching token-vault endpoint region. | Card details and network tokens can be forwarded; network-token fallback requires an Adyen token for the same card.Source 23 |
The migration guide stages the move: route new tokenizations to Adyen, import existing customer details, then change the recurring-charge process. Tokens created at the old provider during the transition also need to be captured. This preserves the distinction between transferring stored credentials and switching live charges.[22]
Data processing and retention
| Data or function | Documented treatment | Limit |
|---|---|---|
| Acquiring transaction data | Adyen acts as controller; transaction records are normally retained for seven years after the transaction concludes in most jurisdictions. | Local law, administration and unresolved legal claims can extend retention.Source 29 |
| Customer relationship and KYC records | The compliance notice describes seven years after contract end for relationship records, and typically five years for identity documents, including biometric identifiers. | The notice does not assign one universal start date to every identity document; local legal requirements govern.Source 30 |
| Payment-specific erasure | Data Protection API targets shopper data for an original payment reference; SUCCESS means the request is accepted for asynchronous processing. | forceErasure can bypass an active recurring-token block but does not cancel the recurring transaction.Source 31 |
The general controller notice provides for transfers outside the EEA with contractual safeguards, including standard contractual clauses. It does not promise that every service stays within one country. Its privacy route covers access, correction and erasure requests, subject to legal exceptions. For compliance processing, Adyen also describes ongoing monitoring and machine-learning use for fraud, risk and service improvement.[28][30]
Support and service availability
Sections ↑Adyen documents round-the-clock urgent support across time zones. The Customer Area is the primary ticket route and also exposes local support telephone numbers. Tickets can include transaction references, API errors, integration versions, payout currencies and report or batch identifiers, allowing the issue to be tied to the correct account and payment event. Its public status service records incidents, and service-status notifications can be subscribed to in the Customer Area.[24]
The merchant terms use commercially reasonable efforts for 99.9% quarterly-average Payment Interface availability, measured by receipt of transaction messages. Exclusions include merchant or banking/scheme actions, general internet failures, individual payment-method failures, requested changes and force majeure. Customer Area maintenance is separate from that measurement.[16]
Official contact routes
Entities and financial permissions
Sections ↑Adyen N.V. appears in De Nederlandsche Bank’s current bank register as a credit institution, relation F0001, with Dutch company number 34259528 and statutory seat Amsterdam. The register includes country-specific EEA passport entries for banking and payment activities, including acquiring and foreign exchange. Those entries identify regulated activities and territories; the merchant eligibility policy above governs the separate commercial question of accepting a particular trading business.[26]
Operator and regional scope
| Entity or disclosure | Scope | Evidence |
|---|---|---|
| Adyen N.V. | Dutch credit institution; applicable EEA passport activities. | Current DNB bank register.Source 26 |
| Adyen N.V., UK branch | Adyen identifies a Part 4A-authorised overseas branch under PRA and FCA supervision. | Provider’s current EMEA legal disclosure.Source 27 |
| Adyen MEA FZ-LLC | Adyen identifies a UAE Category II Retail Payment Services Licence, number 08.01.02.035.2026.02. | Provider’s current EMEA legal disclosure.Source 27 |
The merchant agreement defines the supplier as Adyen N.V. and relevant local affiliates where the services or local law require them. It ordinarily continues indefinitely, with either party able to terminate on at least two months’ written notice unless a different arrangement is agreed.[16]
Company and current development
Sections ↑Adyen was founded in Amsterdam in 2006. Its published history records expansion into risk tools in 2010, point-of-sale payments in 2012, platforms in 2016 and issuing in 2019. That development explains the breadth of the present offering: an online checkout sits alongside acquiring, payment data, financial accounts and outbound money movement.[32]
Adyen is based in Amsterdam and identifies regional headquarters in San Francisco, Singapore and São Paulo. Its 13 August 2026 results release identifies the company as AMS: ADYEN and reports EUR 803.8 billion of processed volume for the first half of 2026. The same release says the Talon.One and Orb acquisitions closed after the half-year end, adding loyalty and usage-based billing capabilities, and describes the introduction of Intelligent Money Movement. These are group developments; they do not change the eligibility classification of a broker’s business.[33][34]
- Operator
- Adyen N.V. and relevant contracting affiliates
- Service scope
- Payment acceptance, acquiring, settlement, payouts and payment-risk tools for approved businesses.
- Customer types
- Enterprises; Financial-services firms; Insurance businesses; Eligible platform businesses
- Delivery
- Hosted; API; Managed service
- Pricing publication
- Public and quoted pricing
- Headquarters
- Amsterdam, Netherlands
- Platforms
- Adyen Customer Area; Adyen Uplift
- Integrations
- Checkout API; Hosted Checkout; Drop-in; Payment webhooks; Disputes API
- Pricing scope
- Public payment-method rates; business-dependent minimum invoice and separately priced additional products.
- Implementation
- Business underwriting, test integration, signed agreement and separately configured live account.
- Support
- Customer Area tickets, local support telephone routes and 24/7 urgent support.
- Permissions and regulatory scope
- Adyen N.V. is a Dutch credit institution; regional permissions and merchant eligibility are separate.
Provider metadata checked 20 Oct 2026Source 32Source 4Source 37Source 26Source 8Source 1Source 5Source 34Source 6Source 2Source 13Source 33Source 19Source 24Source 16Source 3
Additional Information
Sections ↑Payment operations beyond the initial authorisation
| Operational item | Available mechanism | Important distinction |
|---|---|---|
| Cancellation and refund | Customer Area or API actions; cancellation before capture, refund after capture. | The user needs the relevant payment-management permission.Source 35 |
| Payment-list export | CSV download with the Export Payments role. | Shopper identity fields are masked unless Merchant view PII is granted.Source 35 |
| Automated reconciliation files | Scheduled reports trigger REPORT_AVAILABLE with filename and download URL; a report-service credential downloads the file. | Report permissions and account scope are separate; PGP encryption is optional.Source 36 |
| Payout status | Webhooks track booked, pending, credited, accepted or returned states according to route. | Card-network acceptance is not the same event as an instant bank transfer being credited.Source 39 |
Chargebacks have their own lifecycle after the original payment. The Notification of Chargeback begins the defence period, with timing and stages differing by scheme. Adyen debits the disputed amount and chargeback fee, while the issuer assesses the supplied defence. The merchant can follow events through the Customer Area and dispute webhooks.[38]
Disputes can be accepted or defended through the Customer Area or Disputes API. Each booked chargeback carries a fee. Supporting evidence must meet the relevant reason code and deadline; Adyen accepts PDF, JPG or TIFF files but rejects sensitive material such as passport copies, full card numbers and unrelated tax records. Automated defence applies to eligible cases, rather than every disputed payment.[37]
Stopping processing does not immediately release the risk deposit. The deposit remains merchant-owned and is returned progressively after reversal costs, with the documentation describing roughly six months after processing stops once chargeback exposure has ended. This is an exposure-dependent release process, not a guaranteed six-month refund date.[18]
Sources & further reading
- Financial services payment solutions Adyen · Accessed 20 Oct 2026
- Prohibited and restricted products and services Adyen · Accessed 20 Oct 2026
- Adyen Uplift Adyen · Accessed 20 Oct 2026
- Standard payments integration Adyen · Accessed 20 Oct 2026
- Online payment integration flows Adyen · Accessed 20 Oct 2026
- Payouts and Payments Adyen · Accessed 20 Oct 2026
- Merchant settlement and payout models Adyen · Accessed 20 Oct 2026
- Handle webhook events Adyen · Accessed 20 Oct 2026
- API idempotency Adyen · Accessed 20 Oct 2026
- API credentials Adyen · Accessed 20 Oct 2026
- Identity and access management Adyen · Accessed 20 Oct 2026
- API credential roles and card-data requirements Adyen · Accessed 20 Oct 2026
- Payment method pricing Adyen · Accessed 20 Oct 2026
- Visa pricing: United Kingdom website Adyen · Accessed 20 Oct 2026
- Invoice reconciliation guide Adyen · Accessed 20 Oct 2026
- Merchant terms and conditions Adyen · Accessed 20 Oct 2026
- Sales Day Payout terms Adyen · Accessed 20 Oct 2026
- Merchant account deposit Adyen · Accessed 20 Oct 2026
- Set up for Adyen payments Adyen · Accessed 20 Oct 2026
- Live account application requirements Adyen · Accessed 20 Oct 2026
- Online payments go-live checklist Adyen · Accessed 20 Oct 2026
- Import data from another payment provider Adyen · Accessed 20 Oct 2026
- Forward stored payment details Adyen · Accessed 20 Oct 2026
- Service status and support Adyen · Accessed 20 Oct 2026
- Contact sales Adyen · Accessed 20 Oct 2026
- Adyen N.V. bank register entry De Nederlandsche Bank · Accessed 20 Oct 2026
- EMEA licences and disclosures Adyen · Accessed 20 Oct 2026
- Privacy statement Adyen · Accessed 20 Oct 2026
- Privacy: acquiring transaction data Adyen · Accessed 20 Oct 2026
- Privacy: compliance and customer records Adyen · Accessed 20 Oct 2026
- Data Protection API Adyen · Accessed 20 Oct 2026
- Company history Adyen · Accessed 20 Oct 2026
- H1 2026 financial results Adyen · 13 Aug 2026 · Accessed 20 Oct 2026
- Global offices Adyen · Accessed 20 Oct 2026
- Manage payments Adyen · Accessed 20 Oct 2026
- Automatic reports Adyen · Accessed 20 Oct 2026
- Manage disputes Adyen · Accessed 20 Oct 2026
- Dispute flow Adyen · Accessed 20 Oct 2026
- Payout lifecycle Adyen · Accessed 20 Oct 2026
This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.