Payments Architecture for SaaS Founders

Why payment architecture matters for SaaS founders, the three layers of payment systems, and who this guidebook is for.

• Why Payment Architecture Matters Free with email
  9 min

  Imagine building a SaaS product with a polished onboarding flow, powerful features, and a growing waitlist -- but no way for customers to enter their credit card. Users love the demo, but they cannot become paying customers. That is what a product looks like without a well-designed payment architecture. Payment architecture is not a detail you figure out later. It is the plumbing that connects your product to your revenue. Get it right, and money flows smoothly. Get it wrong, and you lose sales, invite compliance headaches, and build technical debt that compounds with every new customer. The Revenue Flow Problem Every dollar your SaaS earns passes through a chain of systems before it reaches your bank account. That chain looks something like this: Customer clicks "Subscribe" on your pricing page Their browser sends payment details to a payment provider The provider verifies the card, checks for fraud, and charges the customer The provider sends a webhook to your server confirming the payment Your server updates the customer's access level in the database The provider deposits money into your bank account (minus fees) Every step in that chain is a separate system with its own…

Understanding Merchants of Record (MoR), payment processors, and platform-integrated solutions. When to use each category.

• Understanding Payment Providers Free with email
  10 min

  Choosing a payment provider is a decision about how much of the transaction you want to own. You can hand the entire sale to a company that becomes the legal seller (Paddle, Gumroad), move the money yourself and stay the seller of record (Stripe, PayPal), or accept whatever payment system is bundled into the platform you already publish on (Shopify, Substack). Each option trades control for convenience at a different price point. Payment providers fall into three categories. Understanding these categories is the single most important decision you will make for your payment architecture, because switching categories later is far more painful than switching providers within the same category. Category 1: Merchants of Record (MoR) What is a Merchant of Record? A Merchant of Record is a company that legally sells your product to the end customer on your behalf. When a customer buys your ebook or SaaS subscription through Gumroad, the customer's credit card statement shows "GUMROAD" -- not your company name. Gumroad is the legal seller. You are the supplier. Concretely: you build the product, and the MoR runs the charge, the receipt, the refund, the chargeback, and the tax registration…

A decision framework for selecting providers based on your business model, geography, volume, and resources.

• Decision Framework Free with email
  10 min

  The Architecture Question That Matters Most Not "which payment provider is best." That question has no single answer. The right question is: given your specific situation, which payment architecture gets you to revenue fastest with the least risk? A solo founder in Germany selling a $9/month tool has fundamentally different needs than a Series A startup in San Francisco processing $500K/month across 30 countries. Both need payments. Neither should use the same architecture. Choosing a payment architecture is like choosing a car: a solo commuter does not need a cargo van, and a delivery company cannot run on a sedan. This chapter gives you a decision framework, not a recommendation. By the end, you will know which path fits your situation and why. The Big Decision: MoR vs Processor Before picking a specific provider, answer one question: do you want to be the merchant of record, or do you want someone else to handle that? Merchant of Record (MoR) The MoR (Paddle, Gumroad, Polar.sh) is the legal seller. They collect payment, handle taxes, issue refunds, and remit VAT/sales tax. The customer sees the MoR on their credit card statement, not your company. The practical consequence: your…