{"id":6850,"date":"2026-10-28T09:27:00","date_gmt":"2026-10-28T09:27:00","guid":{"rendered":"https:\/\/www.kindgeek.com\/blog\/?p=6850"},"modified":"2026-10-29T08:29:15","modified_gmt":"2026-10-29T08:29:15","slug":"build-vs-buy-adyen-for-platforms","status":"publish","type":"post","link":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms","title":{"rendered":"Build vs buy on Adyen for Platforms: the real cost of a sub-merchant portal"},"content":{"rendered":"\n<p>Adyen\u2019s Platforms segment brought in <a href=\"https:\/\/www.adyen.com\/press-and-media\/adyen-publishes-q1-2026-business-update-4gyhh5\" target=\"_blank\" rel=\"noreferrer noopener\">\u20ac75.0<\/a> million of net revenue in Q1 2026, up 40% year on year at constant currency. Every tenant on Adyen for Platforms can onboard sellers and move money as soon as its integration is in place. The businesses underneath it, the salon and the restaurant and the personal trainer, usually have no sub-merchant portal to sign in to.<\/p>\n\n\n\n<p>That gap gets filled one of two ways. Either the platform\u2019s own team answers \u201cwhere is my payout\u201d by hand, or someone builds a portal. Most platforms assume they will build it, and the build is rarely as contained as the first estimate suggests. Getting embedded payments live is the easy half.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What a sub-merchant portal on Adyen for Platforms has to do<\/h2>\n\n\n\n<p>A sub-merchant portal looks like a dashboard. It behaves like a translation layer over a financial system you do not control.<\/p>\n\n\n\n<p>Adyen records payment and account states in its own terms. A seller does not want to read those terms, and your support team should not be reading them aloud over email. \u201cVerification pending\u201d is worthless to a seller on its own. It becomes useful only when they can see why it is pending and what action clears it. That translation, applied to every status in the system, is the actual product. The screens are what it gets delivered in.<\/p>\n\n\n\n<p>Take a Monday morning on a live platform. A seller logs in to check why her payout is short. An operations lead figures out which new sellers from last week didn\u2019t finish signing up. Behind the scenes, all those sellers went through an onboarding flow that had to match Adyen\u2019s business verification needs. In Collimate, our <a href=\"https:\/\/www.kindgeek.com\/submerchant-portal-adyen-for-platforms\">sub-merchant portal<\/a> for Adyen for Platforms, each of these tasks has its own dedicated area:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The sub-merchant portal lets that seller from Monday morning see why her payout is short. Each payment appears in her transaction list with the fee already deducted, so she can find the answer herself instead of emailing support. The portal needs to work for quick checks on a phone and for detailed reviews at the end of the month.<\/li>\n\n\n\n<li>The tenant admin panel lets your operations lead see all sub-merchants on one screen, including any tricky cases. For example, a seller might pass verification but still cannot receive payouts. From her perspective, everything is complete, but her money is not arriving. If your ops lead has to check Adyen directly to figure this out, the panel is not doing its job.<\/li>\n<\/ul>\n\n\n\n<p>PCI scope is the thing to settle before any of this gets built. Card details are entered through Adyen\u2019s hosted components, so card data never touches the portal\u2019s infrastructure and the portal stays out of scope. Render a card field yourself, once, anywhere in the flow, and you have taken on a PCI DSS obligation nobody budgeted for and your security team inherits.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sub-merchant onboarding follows Adyen\u2019s legal-entity model<\/h3>\n\n\n\n<p>Sub-merchant onboarding follows Adyen\u2019s order of operations, set by its legal-entity model, and that order is not what a signup form suggests. A sole trader has to exist as a person first, then as a business linked to that person. A company needs a record for each owner and signatory behind it, each verified separately. Design your own form around one \u201cbusiness owner\u201d field and the first company with three signatories sends you back to rework it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The honest build estimate: six to seven people for six months<\/h2>\n\n\n\n<p>Our estimate for this scope is a team of six or seven: frontend, backend, an engineer who owns the Adyen integration, QA, a business analyst, a PM and a designer, with fintech experience spread across the group. Six months to a first release, assuming the team is capable and working closely with Adyen\u2019s technical contacts. \u00a3300,000 to \u00a3500,000 to build.<\/p>\n\n\n\n<p>Two caveats on the number. It covers a first release, not the steady state. And it assumes the estimate holds.<\/p>\n\n\n\n<p>This range comes from our own delivery experience, which is not a published benchmark. Use it as a starting point for your own calculations, because everything depends on your own requirements.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"563\" src=\"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1024x563.png\" alt=\"Four delivery phases totalling 4 to 5 weeks: model fit, tenant provisioning, validation on test and production cutover\" class=\"wp-image-6855\" srcset=\"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1024x563.png 1024w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-300x165.png 300w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-768x422.png 768w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-360x198.png 360w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image.png 1252w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Why building a sub-merchant portal in-house runs over budget<\/h2>\n\n\n\n<p>When an IT project goes badly wrong, it does not go 50% wrong. The average one in that group costs 5.53 times what it was supposed to.<\/p>\n\n\n\n<p>That comes from <a href=\"https:\/\/doi.org\/10.1177\/87569728251340590\">5,360<\/a> IT projects studied by Flyvbjerg and colleagues in Project Management Journal this year. Roughly four in ten went over budget at all, and plenty of those were the ordinary, absorbable kind. The minority is what matters: nearly one in five blew past the estimate by more than half, and it is that group whose average lands at 5.53 times.<\/p>\n\n\n\n<p>So an IT budget has no typical overrun to plan around. Of the 23 kinds of project compared, IT was the only one with no stable average at all, which is another way of saying you cannot add a contingency percentage when the failures have no characteristic size.<\/p>\n\n\n\n<p>The study\u2019s word for what separates the two groups is bespokeness. On an Adyen build, it tends to surface around month four, when the team finds that the seller model they designed against does not map cleanly onto Adyen\u2019s legal entities, that sole traders and multi-director companies need different onboarding paths, and that the verification status they had treated as a field is really a sequence of capability grants arriving by webhook. None of that was in the spec. We have to build all of it before anyone logs in. Therefore, a six-month estimate starts being wrong.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The cost that starts on go-live: API changes and payout support<\/h2>\n\n\n\n<p>Adyen versions its <a href=\"https:\/\/docs.adyen.com\/development-resources\/versioning\" target=\"_blank\" rel=\"noreferrer noopener\">APIs<\/a> and ships a new version whenever a change would break existing integrations. Good API design, and a standing commitment for whoever maintains your portal. Versions 1 and 2 of the Transfers API are already deprecated; current balance platform integrations run on <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfers\/4\/overview\" target=\"_blank\" rel=\"noreferrer noopener\">v4<\/a>.<\/p>\n\n\n\n<p>The legal-entity model is the other moving part. If you mapped Adyen\u2019s entity requirements into your own schema during implementation, every change to those requirements becomes a migration in your system rather than a passthrough. Mirroring the model one to one is more work on day one and considerably less work in year two.<\/p>\n\n\n\n<p>A marketplace payout comes in lighter than the salon owner expected. She emails your support inbox, and someone opens Adyen, pulls her week\u2019s payments, adds up the fee your split rule took from each one, and writes back with the total. That is one seller, one week. Your platform will have hundreds of sellers, sometimes a few thousand.<\/p>\n\n\n\n<p>None of that appears in the build estimate. All of it competes with your core product for the same engineers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Build vs buy: in-house vs Collimate, criterion by criterion<\/h2>\n\n\n\n<figure class=\"wp-block-table has-small-font-size\"><table class=\"has-fixed-layout\"><thead><tr><th>Criterion<\/th><th>Build in-house<\/th><th>Collimate<\/th><\/tr><\/thead><tbody><tr><td>Time to first release<\/td><td>6+ months of engineering<\/td><td>4 to 5 weeks across four delivery phases<\/td><\/tr><tr><td>Engineering team<\/td><td>Six to seven people, including QA, BA, PM and design<\/td><td>None to hire. You provide the Adyen API keys<\/td><\/tr><tr><td>Upfront cost<\/td><td>Estimated \u00a3300\u2013500k to build<\/td><td>A one-off setup fee<\/td><\/tr><tr><td>Ongoing cost<\/td><td>Engineering maintenance, plus a roadmap of its own<\/td><td>A monthly subscription based on platform size, such as active sub-merchant count, rather than transaction volume<\/td><\/tr><tr><td>Adyen API changes<\/td><td>Your team tracks and implements every change<\/td><td>Handled inside the product<\/td><\/tr><tr><td>Adyen legal-entity model<\/td><td>Mapped into your schema during implementation<\/td><td>Onboarding already mirrors it one to one<\/td><\/tr><tr><td>Status display<\/td><td>Designed as part of the portal build<\/td><td>Every status carries a reason and a next action by default<\/td><\/tr><tr><td>Cardholder data<\/td><td>In your PCI scope unless you integrate hosted components<\/td><td>Adyen\u2019s hosted components. Card data never reaches the portal<\/td><\/tr><tr><td>Codebase<\/td><td>Yours, along with every line you maintain<\/td><td>One shared codebase, configured per tenant, never forked per client<\/td><\/tr><tr><td>System of record<\/td><td>Adyen, plus whatever you store yourself<\/td><td>Adyen, for funds, card data and the ledger<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>There are four delivery phases: model fit (1 week), tenant provisioning (1 to 2 weeks), testing with a real test seller (1 week), and production cutover using your production keys (1 week). Most of the time is spent on configuration, not building from scratch, which is why it takes weeks instead of months.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who owns what: funds, KYB verification and the interface<\/h2>\n\n\n\n<p>Take the question a compliance lead would ask: can this portal touch a seller\u2019s money? It cannot. The portal reads the seller\u2019s balance from Adyen and sends payout instructions back, and the money never passes through it. Most of the table below works the same way, and it works that way whether you build or license.<\/p>\n\n\n\n<figure class=\"wp-block-table has-small-font-size\"><table class=\"has-fixed-layout\"><thead><tr><th>Boundary<\/th><th>Owner<\/th><\/tr><\/thead><tbody><tr><td>Funds and balances. The portal never receives or holds money. It reads balances and payout information from Adyen and sends payout instructions back.<\/td><td>Adyen<\/td><\/tr><tr><td>KYB verification and KYC decisions. The portal collects onboarding information in Adyen\u2019s legal-entity format and passes it on.<\/td><td>Adyen<\/td><\/tr><tr><td>Cardholder data. Entered through Adyen\u2019s hosted components, so it stays outside the portal\u2019s PCI scope.<\/td><td>Adyen<\/td><\/tr><tr><td>Capability grants, issued after verification. The portal shows the current status to the seller.<\/td><td>Adyen<\/td><\/tr><tr><td>API credentials. You provide the keys, with test and production kept separate.<\/td><td>Your platform<\/td><\/tr><tr><td>The interface: portal, admin panel and onboarding, plus turning Adyen\u2019s statuses into something sellers can act on.<\/td><td>Kindgeek<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Your brand is the exception, and it is the part sellers actually see. It is a white-label portal where your logo, colours, typeface, and subdomain are set when we stand the tenant up. A seller signs in at your address and never sees ours, even though the code underneath is the same code every other tenant runs.<\/p>\n\n\n\n<p>Another question is what happens if you leave. The sub-merchant portal only reads the payment records and does not keep its own copy. Therefore, all your transaction data stays in an Adyen account. You can switch off the portal, and your records will still be there.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"563\" src=\"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1-1024x563.png\" alt=\"Four delivery phases totalling 4 to 5 weeks: model fit, tenant provisioning, validation on test and production cutover\" class=\"wp-image-6856\" srcset=\"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1-1024x563.png 1024w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1-300x165.png 300w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1-768x422.png 768w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1-360x198.png 360w, https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/image-1.png 1252w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">When not to buy a sub-merchant portal<\/h2>\n\n\n\n<p>Three situations in a build vs buy decision where building, or doing nothing, beats licensing the software.<\/p>\n\n\n\n<p>Your sub-merchants are private individuals. The onboarding flow follows Adyen\u2019s legal-entity model, which is designed around registered businesses. If your sellers are individuals, the model does not fit.<\/p>\n\n\n\n<p>Your sellers run their own finance systems. A business with its own accounting stack may want a data feed, not a login. A portal solves a problem they do not have.<\/p>\n\n\n\n<p>You have in-house payments engineering and the portal is your differentiator. If what your sub-merchants see is the reason they choose you, and you employ people who have integrated Adyen for Platforms before, build it closer to your own product.<\/p>\n\n\n\n<p>It is also not a drop-in for another PSP. The onboarding is mirrored to Adyen\u2019s model specifically.<\/p>\n\n\n\n<p>Everything else is the ordinary case. The portal is table stakes, your sellers expect it because comparable platforms have it, and you are deciding whether to spend six months and most of half a million reaching parity, then paying every year to stay there.<\/p>\n\n\n\n<p>The build vs buy question was never whether your engineers could build it. It is whether this is where you want six months of their time.<\/p>\n\n\n\n<div class=\"wp-block-quick-and-easy-faqs-faqs-only\">            <div class=\"qae-faqs-container qae-faqs-toggle-container\">\n\t\t\t\t\t\t\t<ul class=\"qe-faqs-filters-container\">\n\t\t\t\t<li class=\"active\"><a class=\"qe-faqs-filter all-faqs\" href=\"#\" data-filter=\"*\">All<\/a><\/li>\n\t\t\t\t<li><a class=\"qe-faqs-filter\" href=\"#Build vs Buy submerchant\" data-filter=\".Build vs Buy submerchant\">Build vs Buy submerchant<\/a><\/li>\t\t\t<\/ul>\n\t\t\t\t\t<div id=\"qaef-6873\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> What size of platform is this built for?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Hundreds to a few thousand sub-merchants, with someone on your side responsible for seller operations.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6872\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> How is pricing set?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>A one-time setup fee plus a monthly subscription based on platform size, such as the number of active sub-merchants, rather than transaction volume. For platforms still ramping up, the setup fee and the subscription can be balanced differently.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6871\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> How long does it take to go live?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Weeks rather than quarters, because the tenant is configured rather than built. The four delivery phases above show how that time is spent.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6870\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Can the portal be white-label?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Yes. Logo, palette, type and a dedicated subdomain per tenant, configured at provisioning. Sub-merchants sign in to something that carries your brand, and the codebase stays shared.<br><\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6869\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Is cardholder data ever in scope?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>No. Payment interfaces are Adyen\u2019s hosted components, so card data never reaches the portal\u2019s infrastructure and is not in its PCI scope.<br><\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6868\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Who makes the KYB verification decision?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Adyen. We collect onboarding data in Adyen\u2019s legal-entity shape and pass it on. The outcome, and the capability grant that follows it, are Adyen\u2019s. We surface the result and the reason.<\/p>\n\n\n\n<p><\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6867\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Does the portal touch our money?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>No. It never receives, holds or transmits funds. Balances and payouts are read through from Adyen and instructed back to it.<\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div id=\"qaef-6866\" class=\"qe-faq-toggle build-vs-buy-submerchant\">\n\t\t\t<div class=\"qe-toggle-title\">\n\t\t\t\t<h4>\n\t\t\t\t\t<i class=\"fa fa-minus-circle\"><\/i> Do we need to already be on Adyen for Platforms?\t\t\t\t<\/h4>\n\t\t\t<\/div>\n\t\t\t<div class=\"qe-toggle-content\">\n\t\t\t\t\n<p>Yes, live or contracted. The portal is a layer on your own embedded payments setup on Adyen, not a payment provider and not an alternative to one. That is the one firm requirement.<\/p>\n\n\n\n<p><\/p>\n\t\t\t<\/div>\n\t\t<\/div>\n\t\t            <\/div>\n\t\t<\/div>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Adyen\u2019s Platforms segment brought in \u20ac75.0 million of net revenue in Q1 2026, up 40% year on year at constant currency. Every&#8230;<\/p>\n","protected":false},"author":24,"featured_media":6852,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[24,361],"tags":[],"class_list":{"0":"post-6850","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-fintech","8":"category-sub-merchant-portal"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Adyen for Platforms: Build vs Buy a Sub-Merchant Portal<\/title>\n<meta name=\"description\" content=\"Building a sub-merchant portal on Adyen for Platforms takes time and a team. See the build-vs-buy trade-offs, ownership, and when not to buy.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Adyen for Platforms: Build vs Buy a Sub-Merchant Portal\" \/>\n<meta property=\"og:description\" content=\"Building a sub-merchant portal on Adyen for Platforms takes time and a team. See the build-vs-buy trade-offs, ownership, and when not to buy.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms\" \/>\n<meta property=\"og:site_name\" content=\"Kindgeek\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-28T09:27:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-29T08:29:15+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/build-vs-buy-adyen-for-platforms-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Kateryna Shykula\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kateryna Shykula\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Adyen for Platforms: Build vs Buy a Sub-Merchant Portal","description":"Building a sub-merchant portal on Adyen for Platforms takes time and a team. See the build-vs-buy trade-offs, ownership, and when not to buy.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms","og_locale":"en_US","og_type":"article","og_title":"Adyen for Platforms: Build vs Buy a Sub-Merchant Portal","og_description":"Building a sub-merchant portal on Adyen for Platforms takes time and a team. See the build-vs-buy trade-offs, ownership, and when not to buy.","og_url":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms","og_site_name":"Kindgeek","article_published_time":"2026-10-28T09:27:00+00:00","article_modified_time":"2026-10-29T08:29:15+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/build-vs-buy-adyen-for-platforms-1.png","type":"image\/png"}],"author":"Kateryna Shykula","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kateryna Shykula","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#article","isPartOf":{"@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms"},"author":{"name":"Kateryna Shykula","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/person\/ca19cd7da9cbba3d1174d3291891c4cc"},"headline":"Build vs buy on Adyen for Platforms: the real cost of a sub-merchant portal","datePublished":"2026-10-28T09:27:00+00:00","dateModified":"2026-10-29T08:29:15+00:00","mainEntityOfPage":{"@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms"},"wordCount":1873,"publisher":{"@id":"https:\/\/www.kindgeek.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#primaryimage"},"thumbnailUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/build-vs-buy-adyen-for-platforms-1.png","articleSection":["FinTech","Sub-Merchant Portal"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms","url":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms","name":"Adyen for Platforms: Build vs Buy a Sub-Merchant Portal","isPartOf":{"@id":"https:\/\/www.kindgeek.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#primaryimage"},"image":{"@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#primaryimage"},"thumbnailUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/build-vs-buy-adyen-for-platforms-1.png","datePublished":"2026-10-28T09:27:00+00:00","dateModified":"2026-10-29T08:29:15+00:00","description":"Building a sub-merchant portal on Adyen for Platforms takes time and a team. See the build-vs-buy trade-offs, ownership, and when not to buy.","breadcrumb":{"@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#primaryimage","url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/build-vs-buy-adyen-for-platforms-1.png","contentUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/build-vs-buy-adyen-for-platforms-1.png","width":1200,"height":630,"caption":"Build vs buy on Adyen for Platforms: the real cost of a sub-merchant portal, shown as a fork between Build and Buy"},{"@type":"BreadcrumbList","@id":"https:\/\/www.kindgeek.com\/blog\/build-vs-buy-adyen-for-platforms#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.kindgeek.com\/blog"},{"@type":"ListItem","position":2,"name":"Build vs buy on Adyen for Platforms: the real cost of a sub-merchant portal"}]},{"@type":"WebSite","@id":"https:\/\/www.kindgeek.com\/blog\/#website","url":"https:\/\/www.kindgeek.com\/blog\/","name":"Kindgeek","description":"Blog | Kindgeek","publisher":{"@id":"https:\/\/www.kindgeek.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.kindgeek.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.kindgeek.com\/blog\/#organization","name":"Kindgeek","url":"https:\/\/www.kindgeek.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/02\/kg-logo-updated.png","contentUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/02\/kg-logo-updated.png","width":300,"height":60,"caption":"Kindgeek"},"image":{"@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/person\/ca19cd7da9cbba3d1174d3291891c4cc","name":"Kateryna Shykula","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kindgeek.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/make-a-portrait-variations-from-differen_k-h8QYBiRAOUpRUJ8e5R3Q_NaReDJUDS2GbFznSvXbaIg-150x150.jpg","contentUrl":"https:\/\/www.kindgeek.com\/blog\/wp-content\/uploads\/2026\/10\/make-a-portrait-variations-from-differen_k-h8QYBiRAOUpRUJ8e5R3Q_NaReDJUDS2GbFznSvXbaIg-150x150.jpg","caption":"Kateryna Shykula"},"description":"Content Producer at Kindgeek","sameAs":["https:\/\/www.linkedin.com\/in\/shykulacath\/"],"url":"https:\/\/www.kindgeek.com\/blog\/author\/kateryna-shykula"}]}},"_links":{"self":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts\/6850","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/comments?post=6850"}],"version-history":[{"count":7,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts\/6850\/revisions"}],"predecessor-version":[{"id":6876,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/posts\/6850\/revisions\/6876"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/media\/6852"}],"wp:attachment":[{"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/media?parent=6850"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/categories?post=6850"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kindgeek.com\/blog\/wp-json\/wp\/v2\/tags?post=6850"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}