Collimate is a white-label sub-merchant portal for platforms on Adyen for Platforms. Adyen stays the system of record; Collimate is the interface your sub-merchants and your team use on top of it. The board below shows what is live, what is in delivery with a target quarter, what we will scope when a platform needs it, and what we commit to along the way.
Last updated 14 October 2026
Reviewed quarterly
Version 2
01 / At a glance
15 features live today. 17 more on the way.
Phase 2 and Phase 3 are part of the subscription. No upgrade fee when a feature ships; every platform on the current version gets it.
LivePhase 1 · 15 features
Core embedded payments.
Everything a sub-merchant needs to get verified, get paid and see where the money went, and everything a platform needs to run it, including a platform that already has sub-merchants on Adyen.
Adyen hosted onboarding inside your branded portal, or API onboarding where your own flow collects the data. A remediation loop when Adyen asks for more information. Status shown with its reason and next action. Invite-only today.
Payouts: schedule, history and balance
When they are paid, what was paid, what is pending, read from the Adyen balance account. Sub-merchants pick a payout schedule the platform has published.
Transactions with fees and splits
Platform fee and sub-merchant share side by side, filterable, so reconciliation does not need a ticket.
Stores and payment methods
Create and manage stores in the currency they trade in; choose payment methods per store within the set the platform enables. Payment pages stay with Adyen or with the platform's own storefront; Collimate does not sit in the card data flow.
Payment links
Sub-merchants create and share Adyen payment links for payments taken outside a storefront, per store and per currency. A link closes once it is paid; the payment appears in the transactions list.
Team members
A sub-merchant invites colleagues to the same account. Everyone has the same level of access today; owner, finance and read-only roles arrive in Phase 2.
Dashboard and sign-in
Balance, recent activity and verification state on one screen. Sign-in and password reset inside the portal.
Platform admin · 6
Balance platform connection and setup
Connect your Adyen balance platform with credentials you enter yourself, enable payment methods, manage admin users, apply branding. One licence covers all regions; an extra balance platform is a one-off configuration.
Import of an existing portfolio
For platforms already live on Adyen for Platforms: import account holders, legal entities, balance accounts and split configuration, then invite sub-merchants in waves, five first, then the rest. Transaction history is read live from Adyen from the first sign-in, so nothing is migrated by hand.
Sub-merchant management
Invite, track verification progress, open any account and see what the sub-merchant sees.
Split profiles per store
Define the platform / sub-merchant split once as a profile, set a default for new stores and assign exceptions per store.
Portfolio overview
Volume, sub-merchant counts and payout totals across the portfolio, traceable to Adyen records, with the gaps surfaced: missing split configuration, stuck onboarding.
Audit log of admin actions
Every change in the admin panel is recorded with who made it and when, visible on the record itself.
Integration · 2
Hosted branded portal on your domain
Single licence, multiple balance platforms
In developmentPhase 2 · Q4 2026 · 5 features
Money operations and basic roles.
The things a platform asks about first after the demo: giving money back, defending it, reporting on it, and letting more than one person in with the right access. Prioritised from feedback gathered in Adyen for Platforms sessions.
Full and partial refunds against a transaction, visible in the ledger and reflected in the next payout. Until release, refunds run through the platform's existing path.
Disputes and chargeback defence
Open disputes with deadline and reason; accept or challenge, and upload evidence without leaving the portal.
Reports
Downloadable settlement and transaction reports from Adyen reporting, scoped to the sub-merchant's accounts. Monthly statement and payout summary first.
Platform admin · 1
Flexible feature-flag configuration
Portal capabilities switched on or off per tenant from the admin side, so each platform runs only the modules it needs without a separate build.
Sub-merchant portal and platform admin · 1
Roles, basic
Owner, finance and read-only for sub-merchants; admin and support for the platform. Per-store permissions follow in Phase 3.
PlannedPhase 3 · 5 features
Scale and control.
What a platform needs once it has more than a handful of sub-merchants, more than one person running the panel, and more than one market.
Onboarding started from inside the platform's own product: a new sub-merchant begins verification where they already are, without an invitation. Invite-only stays available for platforms that want control over who enters.
Platform admin · 1
Guided migration path
For platforms moving from AFP-managed to balance platforms: import, phased invitations and historical transaction visibility in one guided flow. Until then, migrations run as a scoped project, see below.
Sub-merchant portal and platform admin · 3
Granular permission management
An owner reviews the finances of all their stores; a store manager sees one and actions a refund there. Permissions per store and per action, on top of the Phase 2 roles.
Notification centre
In-portal and email notifications for the events that generate support tickets today: verification outcome, payout sent, dispute opened, refund completed.
Localisation
Portal language and number formatting per tenant. UK English first, then the EU languages platforms ask for.
LaterDemand-led · 7 features
Extend.
Raised in conversations with platform teams. Not sized. Each moves into a phase when a named platform needs it and the technical assessment is done.
Confirming which of Adyen's latest payout capabilities the portal exposes as-is and which need a change.
Assessing
Adyen Capital
Financing offers surfaced to eligible sub-merchants inside their portal, following the same component pattern as payouts. Adyen owns eligibility, compliance and funding; Collimate provides the interface; the platform needs Capital in its Adyen agreement.
Assessing
Card issuing
Cards issued through Adyen, requested and managed from the sub-merchant portal. Issuing must be in the platform's Adyen agreement.
Assessing
Business accounts
Adyen business accounts exposed in the portal alongside balances and payouts. Adyen owns the account; Collimate presents it.
Assessing
Payment terminals
Ordering and managing Adyen terminals from the portal for in-person payments.
Integration · 2
Embedding Collimate inside your product
Portal modules inside a platform's own SaaS interface instead of a separate hosted portal. Authentication hand-off and security boundaries under assessment.
Dates are target quarters. A dated phase can move its quarter; its scope does not shrink.
Next step
Bring every sub-merchant into focus.
We are taking on a small number of design partners: platforms on Adyen for Platforms who want a say in what gets built, direct access to the team building it, and early pricing.
We would like to use analytics cookies from Microsoft Clarity and Google Analytics to understand how this site is used. They load only if you accept. Cookie Policy