Collimate is narrow on purpose. Below is the profile it was built around and the profiles it was not — stated here rather than discovered on a call, because a demo you should not have taken costs you more than it costs us.
- You are live on, or contracted for, Adyen for Platforms
- Built for
- Collimate is a layer on your own Adyen setup, mirrored to its model. It is not a payment provider and not an alternative to one, so this is the one thing that cannot be worked around.
- Your sub-merchants are small businesses
- Built for
- A salon, a clinic, an independent hotel, a restaurant, a shop. A named owner, a bank account, no finance function, and a phone rather than a desk. That is who the portal is designed around.
- You have hundreds to a few thousand of them
- Built for
- Enough that support can no longer absorb the payment questions one at a time, not so many that you have already built a seller dashboard of your own.
- Someone owns seller operations
- Built for
- A person whose actual job is partner or seller operations. They are the one the admin panel is for, and without them a portal gets bought and never adopted.
- Sellers ask where their money is, by email
- Built for
- If nobody is asking, there is nothing here to fix. If your team answers it by opening Adyen on the seller's behalf, that is the workflow this replaces.
- Your sellers are private individuals
- Not for
- Onboarding mirrors Adyen's legal-entity model, which assumes a registered business. Consumer sellers, gig workers and one-off recipients are a different product, and we would rather say so now.
- Your sellers are enterprises
- Not for
- A business with a finance team and a general ledger wants a data feed, not somewhere to log in. The portal solves a problem they do not have.
- You have a payments engineering team
- Not for
- If payments is something you staff rather than something you buy, you will build this, and you will build it closer to your own product than we can.
- You want a theming tool to run yourself
- Not for
- Branding, domain and module policy are configured for you when your tenant is provisioned. That is a deliberate choice, not a gap — it is what keeps every tenant on one maintained codebase.