A Branded Sub-Merchant Portalon Adyen for Platforms

A platform built on Adyen for Platforms can onboard sellers and move money as soon as the integration is in place. We build and configure the layer around it: the portal sub-merchants use, the admin panel for the teams managing them, and an onboarding flow that mirrors Adyen's legal-entity model one to one.

Book a technical call

What We Bring to The Build

€10B+

Processed annually by platforms our engineers have built

200+

Engineers focused on payments and regulated fintech

11+ years

Building acquiring, issuing and KYB onboarding systems

Weeks

From your Adyen keys to a live tenant

Payment Questions Answered in The Portal

Sub-merchants can get answers to payment questions directly in the portal.

Questions arrive by email

“Where is my payout?” “Why is my account limited?” Each answer requires checking the relevant information in Adyen and responding to the seller.

Adyen's state needs translating

Adyen records payment and account states in its own terms. The portal presents the same information in language the seller understands.

Every status explains what comes next

“Verification pending” becomes useful when the seller can see why verification is pending and what action to take next.

What We Build

Adyen holds the funds and manages verification while we build and configure the experience around it. We continue to support and maintain it after go-live.

The sub-merchant portal

Earnings after fees. Transactions with statuses that explain what happened and what comes next. Payout initiation, payout account, and payout schedule. Verification status with the reason and next action. The interface supports both a quick overview and detailed reconciliation.

The tenant admin panel

The full onboarding pipeline in one view: invited, in progress, verified, needs attention, with the reason shown on each row. Admin invites, credential setup, and per-sub-merchant capability visibility keep the pipeline readable without opening Adyen.

Onboarding mirrored to Adyen

We collect onboarding data using Adyen's own legal-entity model and pass it through. That gives you one model to maintain and keeps the onboarding flow aligned when Adyen changes its requirements.

In-House Build and Building with Kindgeek

In-house build

The portal is designed and built from scratch
The team that builds the portal also takes on its ongoing maintenance
Adyen’s legal-entity model is mapped during implementation
Status display is designed as part of the portal build
The security review covers the architecture and components used in the build

Building with Kindgeek

The portal starts from an existing implementation and is adapted to the seller model
One shared codebase supports multiple tenants, with configuration applied per tenant
Onboarding already mirrors Adyen’s legal-entity model
Every status includes a reason and next action by default
Adyen remains the system of record for funds, card data, and the ledger

The Roles Behind the Platform

Funds and balances

The portal does not receive or hold money. It reads balances and payout information from Adyen and sends payout instructions back to Adyen.

Adyen

KYB and KYC decisions

The portal collects onboarding information in Adyen's legal-entity format and passes it to Adyen. Adyen makes the verification decision.

Adyen

Cardholder data

Card details are entered through Adyen's hosted payment components. Card data does not pass through the portal, keeping it outside the portal's PCI scope.

Adyen

Capability grants

Adyen grants capabilities after verification. The portal shows the current status to the seller.

Adyen

API credentials

The platform provides the Adyen API keys we use. The portal operates with those credentials, with test and production environments kept separate.

Platform

The interface

We build the portal, admin panel, and onboarding flow, and turn Adyen's statuses and data into information sellers can understand and act on.

Kindgeek

Is This Setup Right for You?

This setup works for platforms that already use Adyen for Platforms and need a dedicated portal and admin experience for their sub-merchants.

You already use Adyen for Platforms

The portal works with an existing Adyen setup and is not a payment provider itself.

Your sub-merchants are registered businesses

The onboarding flow follows Adyen's legal-entity model, which is designed around registered businesses rather than private individuals.

You manage hundreds or a few thousand sub-merchants

The portal and admin panel are designed for this scale.

Someone manages seller operations

The admin panel gives the person responsible for sub-merchants one place to manage onboarding, status, and account details.

How We Deliver

Model fit

We map your seller model to Adyen's legal-entity model, agree which modules you need, and identify edge cases.

1 week

Tenant provisioning

We set up your instance, subdomain, TLS, branding, modules, and identity on the shared codebase.

1–2 weeks

Validation on test

You invite a test seller and complete onboarding end to end. We verify the flow and confirm that verification statuses work correctly with your test keys.

1 week

Production cutover

We run the same flow with your production keys and hand seller invitations over to your team. We stay involved as you iterate after launch.

1 week

FAQ

Do we need to already be on Adyen for Platforms?

Does the portal touch our money?

Is cardholder data ever in scope?

Who makes the verification decision?

Can it carry our brand?

How long does it take to go live?

When is this not the right fit?

We are on a different provider. Can you still help?

Could this setup work for your platform?

Share your Adyen setup and seller model with us. We'll come back with the scope, timeline, and team needed to build it.

Book a technical call