
September 23, 20263 min readАдминистратор
Flatpay chooses Adyen to expand its acquiring infrastructure
The partnership separates local merchant relationships from payment infrastructure. Embedded-finance products remain an option for later.
On 23 September 2026, Adyen and Flatpay announced a partnership in which Flatpay retains local merchant relationships while Adyen supplies payment infrastructure and acquiring capabilities. The release describes Flatpay's presence in seven European markets and a base exceeding 100,000 merchants. Business accounts, issuing and other embedded-finance products are presented as future possibilities.
One storefront, two operating layers
The arrangement illustrates a specific division of labour. Customer service remains with the company selling an accessible local proposition, while the complex payment infrastructure relies on another provider. For a small merchant, that can be convenient if the experience genuinely remains simple. For the payment company, it changes the expansion problem: entering a market need not mean rebuilding the entire underlying technology layer.
A unified commercial offer still has infrastructure dependencies. When a transaction fails, a payout is delayed or a dispute arrives, the merchant needs one clear owner of the case. If frontline service and processing sit in different organizations, product quality depends heavily on how effectively the necessary information passes between them. That is an assessment of the operating model, not a report of difficulties in this partnership.
The interesting next question is whether simplicity survives the addition of financial features. Acceptance, balances, expense cards and financing can involve different terms and support procedures. If they eventually share one interface, customers will need a clear explanation of each service. Otherwise, the simplicity of the original proposition may erode as the portfolio expands.
The market significance lies in distribution. An infrastructure supplier gains reach through a partner with local merchant relationships; the partner gains a way to expand without reproducing the full payment architecture. The announcement does not establish an immediate launch of every financial product mentioned, or identical pricing in every country. The next substantive evidence will be the particular markets, functions and timelines the partners actually put into production. Those details will show how the division of responsibilities works beyond the initial announcement.
What it means for merchants and PSPs
For a merchant onboarding through this kind of model, the main practical question is who is responsible for what. A contract with a company selling payments under its own brand should answer questions about the parties and the role of the infrastructure partner.
- Who is the acquirer and the contracting party for card acceptance, and who acts as an agent or platform.
- Who holds funds before payout, what the settlement timelines are and when delays or reserves may apply.
- How disputes work: who receives chargeback evidence and within what deadlines.
- Which transaction data the merchant can access directly and in what format it can be exported for reconciliation.
- What happens to terminals, tokens and transaction history if the merchant changes provider.
For PSPs and ISO partners, the announcement illustrates a model in which market expansion is built on someone else's infrastructure. It will probably require a clear escalation path, aligned SLAs and transparent data exchange between frontline support and processing.
Risks and limitations
Relying on a single infrastructure supplier makes the start easier but reduces flexibility: changes to its pricing, risk rules or supported payment methods reach the end customer directly. Adding business accounts and cards would bring separate compliance and safeguarding requirements, which are worth checking service by service.
When choosing such an offer, a merchant should compare not only the rate but also how quickly support resolves real incidents: a delayed payout, a declined transaction, a dispute. A test enquiry before signing often reveals more about the model than a sales presentation.
Comments · 0
No comments yet — be the first.
Log in · log in to leave a comment.