The Complete Glossary of SaaS Payments, Billing, and Merchant of Record Terms

Building a SaaS business involves managing a complex set of operations, including payments, automated billing, and international tax compliance. Whether you are launching a new subscription product or scaling an established platform across borders, this terminology serves as the foundation for making informed decisions about your revenue infrastructure.

Section 1: Revenue and Growth Metrics

1. Annual Recurring Revenue (ARR)

• ARR is the predictable revenue a SaaS business expects to receive annually from its active subscription base.
• It is a primary metric used for valuation and long-term financial planning.
• While ARR typically excludes one-time fees, some companies internally normalize predictable usage patterns into ARR calculations, though accounting practices vary.

2. Monthly Recurring Revenue (MRR)

• MRR is the normalized measure of a company's predictable monthly revenue.
• For businesses with annual plans, the total value is divided by 12 to provide an accurate monthly figure.
• MRR is a sensitive indicator of immediate growth and the direct impact of pricing adjustments.

3. Net Revenue Retention (NRR)

• NRR is the percentage of recurring revenue retained from existing customers over a specific period, including expansion revenue from upgrades and additional seats.
• An NRR above 100% indicates that the existing customer base is growing its spend faster than it is churning.

4. Gross Revenue Retention (GRR)

• GRR measures the percentage of revenue retained from the original customer base without accounting for upsells or expansion.
• It provides a transparent look at core product retention health.
• A high NRR can sometimes mask an underlying churn problem if a few large customers are upgrading significantly, making GRR a vital counter-metric.

5. Customer Lifetime Value (CLV)

• CLV is the total revenue a business can expect from a single customer throughout their entire relationship.
• It is used to determine the maximum sustainable Customer Acquisition Cost (CAC).
• This simplified formula is commonly used operationally, though actual CLV modeling may vary depending on cohort behavior, expansion revenue, and gross margin assumptions: $$CLV = \frac{ARPU \times \text{Gross Margin \%}}{\text{Churn Rate}}$$

6. Average Revenue Per User (ARPU)

• ARPU is the total recurring revenue divided by the total number of active subscribers.
• Tracking ARPU across different geographic segments helps identify which markets are most profitable.

Section 2: Payment Infrastructure and Processing

7. Payment Gateway

• The payment gateway is the technology layer that transmits payment information from your website to the payment processor.
• It encrypts sensitive data and routes transactions for authorization.
• A gateway alone does not handle tax filing or legal liability.

8. Payment Processor

• The processor is the financial institution that handles the technical execution of a transaction.
• It communicates with card networks (such as Visa or Mastercard) and banks to authorize, capture, and settle funds.

9. Merchant Account

• A merchant account is a specialized bank account that allows a business to accept credit and debit card payments.
• Modern platforms often provide an abstraction via platform infrastructure, which can simplify the process for founders compared to individual manual underwriting with local banks.

10. Authorization and Capture

• Authorization is the moment the customer's bank verifies sufficient funds and places a hold on the amount.
• Capture is the subsequent step where the funds are formally transferred to the merchant.

11. Card-Not-Present (CNP) Transaction

• Any transaction where the physical card is not swiped or tapped, covering all SaaS and digital store purchases.
• CNP transactions generally carry specific processing fees due to the inherent risk profile of online sales.

12. Hosted Checkout

• A payment page hosted by the billing provider rather than on your own servers.
• Hosted checkout significantly reduces the operational complexity associated with directly handling sensitive cardholder data.
• It allows for the integration of regional payment systems to support local bank cards natively.

Section 3: The Merchant of Record Model

13. Merchant of Record (MoR)

• The MoR is the legal entity that sells services to the end customer on behalf of a software company.
• The MoR assumes significant responsibility for payment processing, tax collection, remittance, and compliance operations within the scope of the platform agreement.

14. Global Tax Compliance

• This is the process of identifying, collecting, and remitting taxes (VAT, GST, Sales Tax) across different jurisdictions.
• For founders based in the Gulf region selling globally, an MoR structure supports compliance workflows related to US nexus rules and EU VAT obligations.
• This includes managing the 15% VAT in Saudi Arabia and the 5% VAT in the UAE.

15. Legal Seller Responsibility

• In a traditional gateway model, the business is the legal seller and is responsible for any tax errors found during an audit.
• In an MoR model, the platform acts as the legal seller for the transaction, centralizing portions of tax, payment, and compliance operations under the MoR structure.

16. Chargeback Management

• A chargeback is a payment reversal initiated by a customer's bank during a dispute.
• In an MoR model, the platform generally manages the workflow to respond to disputed transactions and manage supporting documentation.

Section 4: Subscription and Billing Management

17. Billing Cycle

• The recurring interval (monthly, quarterly, or annual) at which a customer is charged.
• Founders often use these cycles to offer both low-barrier entry points and high-retention annual discounts.

18. Usage-Based Billing

• A pricing model where customers pay based on their actual consumption, such as API calls or tokens.
• This model aligns pricing more closely with customer consumption.
• It requires a billing engine capable of real-time metering and dynamic invoice generation.

19. Proration

• The process of adjusting a customer's bill when they change plans mid-cycle.
• Proration ensures customers pay accurately for their period of use during upgrades or downgrades.

20. Dunning

• Dunning is the process of automatically retrying failed payments and communicating with customers about the issue.
• Advanced dunning systems may use retry timing optimization and historical payment behavior analysis to improve recovery rates.

21. Involuntary Churn

• Churn caused by payment failures, such as expired cards or insufficient funds, rather than a conscious decision to cancel.
• Involuntary churn represents a significant portion of failed customer retention for many subscription businesses.

22. Voluntary Churn

• When a customer actively chooses to cancel their subscription.
• Automated retention systems may present context-aware offers or subscription alternatives during the cancellation flow to mitigate this loss.

23. Grace Period

• A buffer period after a payment fails during which the customer retains access to the product.
• Grace periods give the dunning system time to attempt recovery before a user's access is interrupted.

Section 5: Delivery and Compliance

24. License Key Management

• The system used to generate and validate activation codes for software or digital products.
• Modern stacks often integrate this with the billing engine to automatically manage access if a subscription lapses or a payment is disputed.

25. PCI DSS Compliance

• The Payment Card Industry Data Security Standard is a set of rules for handling card data securely.
• Most SaaS founders utilize a hosted checkout to manage the operational complexity associated with directly handling sensitive cardholder data.

26. Webhooks

• Webhooks are automated messages sent from a billing platform to an application when an event occurs.
• They ensure an application is updated when a payment is successful or a subscription state changes.

27. Revenue Recognition

• An accounting principle where revenue is recorded when the service is provided, regardless of when cash is received.
• This is critical for accurate financial reporting and investor due diligence.

State-by-State Reference Table

State tax treatment of SaaS and digital goods changes frequently and may vary based on implementation details, customer classification, sourcing rules, local jurisdiction requirements, and evolving administrative guidance. The table below is a simplified high-level reference and should not be treated as legal or tax advice.

How Kiwy.ai Fits Into the Modern Revenue Stack

For founders and developers resident in the Gulf region, implementing these complex systems from scratch can be a significant barrier to international expansion. Utilizing a specialized monetization and billing platform is a strategic way to manage these requirements.

Kiwy.ai is designed specifically for this purpose, acting as a bridge between the product and the global market.

Choosing the Right Infrastructure Path

By centralizing these functions, founders can focus entirely on developing their core product, such as conversational AI agents, while the billing infrastructure manages the technicalities of international revenue.

FAQs

What is the difference between a payment gateway and a merchant of record?

A payment gateway is the technology that moves data, but the business remains the legal seller. A Merchant of Record (Kiwy Option as Global Merchant of Record (MoR)) acts as the legal seller, managing portions of tax collection, remittance, and compliance operations within the scope of the platform agreement.

How should founders in the Gulf handle regional payments?

Supporting regional payment methods and domestic card schemes (Kiwy Option as Local Infrastructure in GCC) is essential for regional operational coverage and ensuring compatibility with local banking habits.

Can I use a Merchant of Record if I already have a local entity?

Yes. Many founders maintain a local entity for regional operations and use a Merchant of Record (Kiwy Option as Global Merchant of Record (MoR)) to manage the international compliance infrastructure for global sales.

What is the goal of an automated retention system?

The goal is to intercept a cancellation attempt and present the user with a tailored alternative, such as a temporary discount or a plan pause, to preserve the customer relationship.

Understanding these terms is the foundation for building a professional revenue engine. In 2026, the goal for any SaaS founder is to automate the technical infrastructure so they can focus entirely on product development and delivering customer value.

Learn more about simplifying your global revenue stack at kiwy.ai.