The platform operator
Sets plans, risk rules and payout schedules, and sees across merchants with access limited by role.
Retail / Ecommerce SaaS Platform
Ecommerce SaaS platform development for software that many merchants sell through
Founders building commerce software for many merchants meet payments questions before code questions: who is the merchant of record, who verifies sellers, who holds funds and who pays a chargeback. Agnotic Technologies designs and builds that commerce layer, from merchant onboarding to payouts, on top of your multi-tenant backend.
Payments model
Chosen before the build
KYB
Merchant verification
Ledger
Payouts that reconcile
Trusted by global innovators
Industry Overview
What is an ecommerce SaaS platform?
An ecommerce SaaS platform is commerce software that many independent merchants run their stores on, with each merchant's catalog, storefront, orders and payouts kept separate. Agnotic Technologies builds the commerce-specific layer: the payments model, merchant onboarding and verification, payouts and reserves, custom domains and the rules for merchant apps.
Who is involved
Who does an ecommerce SaaS platform serve?
Four parties meet on every transaction, and each needs different data and different controls.
Merchants
Set up their catalog, theme, domain and payout bank account, and see only their own stores and data.
Shoppers
Buy from a merchant's store and can dispute a charge with their card issuer, which starts the chargeback path.
The payment partner
The acquirer, processor or provider behind the platform, whose rules shape onboarding, fund flows and reporting.
Industry Challenges
Where do multi-merchant commerce platforms get stuck?
These problems tend to surface after the first few hundred merchants, when they are expensive to fix.
The payments model was set by whichever provider the first engineer integrated, and the platform later finds it carries chargebacks it never priced in.
Merchant verification is a form nobody reviews, so a fraudulent seller takes payments and leaves the platform with the disputes.
Payouts are one nightly transfer with no breakdown, and merchants open tickets to work out what they were paid for.
Refunds after a payout leave negative balances with no rule for recovering them.
Custom domains are added by hand, and certificates expire when the person who set them up moves on.
Merchant apps get access to every merchant's data because extension permissions were never scoped.
Decision table
Which payments model should your platform use?
This choice shapes onboarding, the ledger, support and your risk team, so we make it first, with your payment partner and counsel. The rules of your acquirer and the card brands decide the details.
| Question | Platform as merchant of record | Registered payment facilitator | Connected accounts through a provider |
|---|---|---|---|
| Who the shopper pays | The platform, usually under its own name on the card statement | The payment facilitator, on behalf of the sponsored merchant | The merchant, through an account created on the provider's platform |
| Who onboards and verifies merchants | The platform, as its own suppliers | The payment facilitator, doing due diligence under its acquirer's rules | The provider, through onboarding flows the platform embeds |
| Who holds funds | The platform, which pays merchants under its own contract | The payment facilitator receives settlement and must pay sponsored merchants promptly | The provider holds balances and pays merchants out |
| Who carries chargebacks | The platform | The payment facilitator, for its sponsored merchants, with its acquirer liable for it | Set by the provider's terms and account type; the platform or the merchant |
| The platform's PCI DSS role | A merchant, and a service provider too if it hosts merchants' payment pages | A service provider that must make sure its sponsored merchants comply | Usually smaller, when card data is captured by the provider's hosted fields |
| Fits when | You sell on merchants' behalf and own the customer relationship, refunds included | Card volume justifies registration, a risk team and acquirer oversight | You want to launch quickly and let a provider carry onboarding and fund flows |
Our Approach
How do we build the commerce layer of a SaaS platform?
How to build ecommerce SaaS that survives growth comes down to three rules we hold to.
Decide the payments model first
We work it out with your payment partner and counsel before writing code, because it drives onboarding, the ledger, support and dispute handling.
Keep a ledger, not just payment records
Every charge, refund, fee, dispute and reserve movement is a ledger entry per merchant, and payouts are calculated from the ledger.
Scope everything to the merchant
A merchant ID sits on every record, API token, webhook and app permission. The generic tenancy architecture underneath is covered on our multi-tenant backend page.
Capabilities
Which ecommerce SaaS modules do we build?
Ecommerce SaaS services for the parts that are specific to commerce, built on your existing tenancy and identity layers.
Merchant onboarding and KYB
Business details, owners and bank accounts collected in steps, checked by the platform or the payment partner before payments are switched on.
Payments model integration
Charges, refunds and disputes wired to the model you chose, whether merchant of record, payment facilitator or connected accounts.
Merchant ledger and payouts
Double-entry balances per merchant, payout schedules and a statement for each payout listing the orders and fees behind it.
Reserves and risk holds
Rolling reserves, payout delays and volume limits for new or risky merchants, controlled by rules the operator owns.
Disputes and refunds
Chargeback notices routed to the merchant with evidence deadlines, and refunds that update the ledger before the next payout.
Custom domains and themes
Merchant domains verified by DNS record, certificates issued and renewed automatically, and theme settings per store.
Per-merchant catalog and settings
Each merchant's products, shipping, tax and checkout settings kept separate, with operator defaults merchants can override.
App and extension platform
OAuth scopes per merchant, webhooks and rate limits, so third-party apps see only the stores that installed them.
How It Works
How does a merchant go from signup to first payout?
This is the merchant journey we build. Each step has an owner, a status and an audit record.
Sign up
A merchant account, store, default theme and admin user are created in the merchant's own tenant. Nothing is live yet.
01
1
Verify the business
Legal name, owners, address and bank account are collected and checked, by the platform or the payment partner depending on the model, before card payments are switched on.
02
2
Set up the store and domain
Catalog import, theme, shipping and tax settings, and a custom domain verified by DNS with a certificate issued through ACME.
03
3
Take payments within limits
New merchants start with volume limits or payout holds that relax as their history builds, under rules the operator controls.
04
4
Get paid and reconcile
Each payout lists the orders, refunds, disputes, fees and reserve movements behind it, so the merchant can match it to their bank statement.
05
5
Engineering Stack
What sits under a multi-merchant commerce platform?
The commerce layer, as distinct from the general multi-tenant backend beneath it.
Payments
Payment facilitator or connected-account APIsProvider hosted payment fieldsIdempotent webhook handlers
Merchant risk
KYB and owner identity checksSanctions screeningRisk rules and holds
Money movement
Double-entry merchant ledgerPayout schedulingBank account verification
Storefronts
Theme engineCustom domains with ACME certificatesCDN per merchant domain
Platform
Merchant-scoped APIsOAuth scopes for appsAudit logging
Measured Impact
What should an ecommerce SaaS operator watch?
Measures we build into the operator console from the first release.
Activation
Onboarding completed
Merchants who finish verification and take a first payment.
Payout accuracy
Payouts that reconcile
Payouts that match ledger entries without manual fixes.
Disputes
By merchant
Dispute counts per merchant, so risk rules act early.
Negative balances
Money owed back
Merchants who owe the platform after refunds or chargebacks.
Use Cases
What do founders build on this layer?
Ecommerce SaaS for startups usually starts as one of these products.
01
Vertical store builder
Storefronts for one kind of seller, such as makers, studios or local shops.
02
Marketplace with seller stores
Sellers get their own storefronts and payouts on a shared marketplace.
03
Wholesale platform
Brands sell to retailers through accounts on one platform.
04
Embedded commerce
Selling added inside an existing SaaS product for its customers.
05
Changing payments model
Moving from merchant of record to connected accounts, or the reverse.
06
Ledger and payouts rebuild
Replacing transfer-only payouts with a ledger merchants can reconcile.
Integrations
Which services does the commerce layer connect to?
Chosen with your payment partner, as their requirements drive several of these.
Payments
Acquirer or payment facilitator sponsorConnected-accounts provider
Merchant risk
KYB and identity verification services
Money movement
Bank payout rails
Checkout
Tax calculation service
Custom domains
DNS and ACME certificate authority
Finance
Accounting export
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
General Data Protection Regulation
Implement lawful consent flows, data minimization, and secure processing for global data privacy.
Payment Card Industry (PCI DSS)
Securing payment transactions and protecting cardholder data with industry-best practices.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does an ecommerce SaaS engagement work?
It depends on scope; we agree a fixed first release on the scoping call.
01
Scoping call
We map your merchants, your payment partner and the payments model options in the table above.
02
Money flow design
Ledger accounts, payout rules, reserves and dispute handling agreed with your finance lead and payment partner.
03
Fixed-scope first release
Merchant signup, verification, payments and payouts working end to end for a pilot group.
04
Merchant rollout
Domains, apps and more merchant settings added as merchants join.
05
Support
Payment partner changes, risk rule updates and ledger monitoring under agreed change control.
Facts and sources
Card network rules and standards behind the design
Short facts we design around, each linked to its primary source.
Visa defines a Payment Facilitator as an entity that contracts with an Acquirer to deposit transactions, receive settlement from, or contract with an Acquirer on behalf of a Sponsored Merchant.
Source: Visa Core Rules and Visa Product and Service Rules (18 April 2026), glossaryUnder the Visa Rules, an Acquirer or Payment Facilitator must conduct an adequate due diligence review of a prospective Sponsored Merchant before contracting with it, including a site visit or a suitable alternative.
Source: Visa Core Rules and Visa Product and Service Rules (18 April 2026), 5.2.1.2A Visa Payment Facilitator Agreement must state that the Payment Facilitator is liable for cardholder disputes caused by its Sponsored Merchants and must ensure they comply with PCI DSS.
Source: Visa Core Rules and Visa Product and Service Rules (18 April 2026), 5.3.1.1When a Payment Facilitator receives payment from its Acquirer, the Visa Rules require it to pay or credit its Sponsored Merchant's account promptly after the transaction deposit.
Source: Visa Core Rules and Visa Product and Service Rules (18 April 2026), 1.5.6.2RFC 8555 defines ACME, a protocol that a certificate authority and an applicant use to automate domain verification and certificate issuance, which is how platforms issue certificates for merchants' custom domains.
Source: IETF RFC 8555
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Related platform and payments services
This page covers the commerce layer. These pages cover the layers around it.
Retail software development
The retail industry hub: storefront, B2B, inventory and pricing software Agnotic builds for retail teams.
High-scale multi-tenant SaaS backend
Tenant isolation, shared and dedicated tiers, and safe schema migrations.
Payment gateway integration services
Gateway APIs, tokenization, webhooks and reconciliation.
KYC compliance software
Identity verification and screening workflows, the building blocks of merchant checks.
Order management system software
Order routing and fulfillment for merchants on the platform.
Marketplace app development
Supply onboarding, search, booking and payouts for two-sided marketplaces.
Omnichannel ecommerce engine
Composable commerce for a single enterprise retailer.
More in Retail
More Retail Solutions
Explore other production-grade engineering platforms we deliver across retail.
Cross-Industry Reach
The Same Engineering Patterns, Across Other Industries
The technical patterns behind this platform translate naturally into adjacent verticals.
Frequently Asked Questions
The payments model, how merchants are verified, the ledger and payout rules, reserves and dispute handling, custom domains and themes, and whether third-party apps are in scope. We explain these drivers on the scoping call instead of quoting a fixed price.
Most platforms launch on connected accounts, so a provider carries onboarding and fund flows. Registering as a payment facilitator makes sense once card volume justifies a risk team, acquirer oversight and liability for sponsored merchants. Your acquirer and counsel make that call with you.
We collect business details, owners and bank accounts in steps, run identity, sanctions and bank account checks through the services your payment partner accepts, and keep payments switched off until the merchant passes.
The ledger records it against the merchant. The amount comes out of the next payout or the merchant's reserve, and if the balance goes negative, the recovery rules the operator set take over.
Yes. The merchant adds a DNS record, the platform verifies it and issues a certificate automatically through ACME, and renewals run without anyone remembering to do them.
It depends on scope; we agree a fixed first release on the scoping call, usually signup, verification, payments and payouts for a pilot group of merchants.
No. Agnotic Technologies is a software development services company. We build your ecommerce SaaS platform for you; your company runs it and holds the merchant relationships.
Industries