{"id":1824,"date":"2026-08-20T08:30:42","date_gmt":"2026-08-20T08:30:42","guid":{"rendered":"https:\/\/freitas.eti.br\/?p=1824"},"modified":"2026-08-26T22:12:33","modified_gmt":"2026-08-26T22:12:33","slug":"chapter-7-merchant-domain","status":"publish","type":"post","link":"https:\/\/freitas.eti.br\/pt-br\/chapter-7-merchant-domain\/","title":{"rendered":"Chapter 7 \u2014 Merchant Domain"},"content":{"rendered":"<h2 class=\"wp-block-heading\">The Center of the Ecosystem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Payment platforms are often described through transactions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Approval rates, fraud decisions, authorization latency, settlement cycles and processed volume tend to dominate technical conversations. These metrics are important, but they can hide a more fundamental truth.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A payment platform does not exist because transactions exist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It exists because merchants need to sell.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Merchant Domain represents this business reality inside the architecture. It is the domain responsible for understanding who the merchant is, which products are enabled, how the commercial relationship is configured and which operational rules apply to that merchant across the platform.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Without merchant context, a transaction is incomplete.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The platform may receive an amount, a payment method and a request for authorization, but it still needs to understand the business behind the transaction. Different merchants may have different risk profiles, settlement rules, fee agreements, enabled products and operational constraints.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Merchant Domain provides the context that allows the rest of the platform to make better decisions.<\/p>\n\n\n\n<div class=\"wp-block-uagb-image uagb-block-68f0bd59 wp-block-uagb-image--layout-default wp-block-uagb-image--effect-static wp-block-uagb-image--align-none\"><figure class=\"wp-block-uagb-image__figure\"><img decoding=\"async\" src=\"https:\/\/freitas.eti.br\/wp-content\/uploads\/2026\/07\/chapter7-merchant-domain-1024x576.png\" alt=\"\" class=\"uag-image-1661\" width=\"1200\" height=\"675\" title=\"chapter7-merchant-domain\" loading=\"lazy\" role=\"img\" \/><\/figure><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">More Than a Cadastro<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In many systems, merchant information starts as a registration record.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A name, document number, address, bank account and contact information are stored so the business can operate. While this information is necessary, it represents only the beginning of the merchant relationship.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In a modern payment platform, the merchant is not just a static record.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The merchant is a living business entity with products, configurations, limits, pricing models, risk attributes, settlement preferences and lifecycle states.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A newly onboarded merchant is different from a mature merchant with stable volume. A high-risk segment may require different controls from a low-risk business. A merchant using only payment links may have different needs from one operating in-store terminals, digital checkout and recurring payments.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Merchant Domain exists to model these differences explicitly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This matters because many platform decisions depend on merchant context. Fraud evaluation may consider merchant category and behavior. Authorization routing may depend on enabled products or commercial agreements. Settlement may depend on payout rules and banking information. Analytics depends on merchant segmentation and performance history.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When merchant data is weak, every downstream domain becomes weaker.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Merchant Context and Platform Behavior<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most important roles of the Merchant Domain is providing context to other domains.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A transaction does not happen in isolation. It belongs to a merchant, and that merchant carries business meaning.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, the same transaction amount may represent different risk depending on the type of merchant. A large amount may be normal in one segment and suspicious in another. Settlement timing may depend on commercial agreements. Fees may depend on product configuration. Reporting may depend on merchant hierarchy, segment or business model.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is why merchant information should not be treated as passive data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It actively influences platform behavior.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In PaymentHub, the Merchant Domain becomes the source of truth for the commercial relationship. It allows other domains to consume merchant context without owning merchant responsibilities themselves.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This separation is important.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Fraud Domain should not become responsible for merchant onboarding. The Settlement Domain should not become responsible for maintaining commercial profiles. The Transaction Domain should not become responsible for pricing configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each domain may need merchant information, but the Merchant Domain owns the meaning of that information.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Lifecycle, Products and Configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A merchant relationship changes over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A merchant may be created, validated, enabled, suspended, reactivated or closed. New products may be added. Settlement accounts may change. Risk parameters may be adjusted. Pricing agreements may evolve. Operational restrictions may be applied or removed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">All of these changes affect the platform.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This makes the merchant lifecycle an architectural concern.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If merchant changes are not modeled clearly, the platform becomes vulnerable to inconsistencies. One domain may treat the merchant as active while another still considers it pending. One process may apply outdated fee rules while another has already moved to a new configuration. Analytical reports may lose meaning if merchant segmentation changes are not tracked properly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Merchant Domain helps reduce this risk by creating a clear place for merchant lifecycle and configuration management.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As PaymentHub evolves, this domain can support capabilities such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Merchant onboarding<\/li>\n\n\n\n<li>KYC and validation workflows<\/li>\n\n\n\n<li>Product enablement<\/li>\n\n\n\n<li>Fee configuration<\/li>\n\n\n\n<li>Risk profile management<\/li>\n\n\n\n<li>Settlement profile management<\/li>\n\n\n\n<li>Merchant status lifecycle<\/li>\n\n\n\n<li>Commercial hierarchy<\/li>\n\n\n\n<li>Self-service configuration<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Not every capability needs to exist from the beginning.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What matters first is recognizing that these responsibilities belong together because they describe the commercial relationship between the platform and the merchant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Merchant Comes After Settlement in the Series<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">From a business perspective, the merchant is the beginning of the story.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From an operational transaction perspective, however, the merchant context is often noticed only after the reader understands the rest of the payment journey. This is why the PaymentHub series first follows the transaction through coordination, fraud, authorization and settlement before returning to the Merchant Domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This editorial choice mirrors a common learning journey.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many people first understand payments through the transaction flow. They see the request, the approval, the decline and the settlement. Only later do they realize that the merchant relationship influences almost every decision made along the way.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In architecture, this realization is important.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The merchant is not simply another participant in the platform.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The merchant is the reason the platform exists.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every transaction, risk evaluation, authorization, settlement event and analytical view ultimately exists to support a merchant&#8217;s ability to sell, receive funds and understand business performance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Nota do Arquiteto<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A practical way to evaluate the maturity of a payment platform is to look at how it treats merchant information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Immature platforms often treat merchant data as registration data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mature platforms treat merchant context as a strategic capability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The difference is significant. Registration data tells the platform who the merchant is. Merchant context tells the platform how it should behave in relation to that merchant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is why the Merchant Domain should not be reduced to a simple database table or administrative module.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is one of the most important sources of business meaning in the entire architecture.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Looking Ahead<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Merchant Domain brings the platform back to its business foundation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After exploring transaction coordination, fraud evaluation, authorization and settlement, it becomes clear that none of these capabilities exist in isolation. They all depend, directly or indirectly, on the merchant relationship.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The next chapter moves from business context to business learning.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once transactions are processed, risks are evaluated, authorizations are obtained, settlements are prepared and merchants are served, the platform begins to accumulate something extremely valuable: data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Analytics Domain exists to transform that data into insight.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>","protected":false},"excerpt":{"rendered":"<p>The Center of the Ecosystem Payment platforms are often described through transactions. Approval rates, fraud decisions, authorization latency, settlement cycles and processed volume tend to dominate technical conversations. These metrics are important, but they can hide a more fundamental truth. A payment platform does not exist because transactions exist. It exists because merchants need to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_uag_custom_page_level_css":"","_monsterinsights_skip_tracking":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[9],"tags":[15],"class_list":["post-1824","post","type-post","status-publish","format-standard","hentry","category-paymenthub-architecture-series","tag-paymenthub-softwarearchitecture-ddd-payments-aws-cloudarchitecture-platformengineering"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"trp-custom-language-flag":false},"uagb_author_info":{"display_name":"Freitas","author_link":"https:\/\/freitas.eti.br\/pt-br\/author\/robertofreitas-eti-br\/"},"uagb_comment_info":0,"uagb_excerpt":"The Center of the Ecosystem Payment platforms are often described through transactions. Approval rates, fraud decisions, authorization latency, settlement cycles and processed volume tend to dominate technical conversations. These metrics are important, but they can hide a more fundamental truth. A payment platform does not exist because transactions exist. It exists because merchants need to&hellip;","_links":{"self":[{"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/posts\/1824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/comments?post=1824"}],"version-history":[{"count":1,"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/posts\/1824\/revisions"}],"predecessor-version":[{"id":1825,"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/posts\/1824\/revisions\/1825"}],"wp:attachment":[{"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/media?parent=1824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/categories?post=1824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/freitas.eti.br\/pt-br\/wp-json\/wp\/v2\/tags?post=1824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}