Tilled

Q1: What is the best way for a software platform to add payment processing and start earning revenue from transactions?

# Adding Payment Processing to a Software Platform

## Core Approaches

**1. Embedded Payments (Payment Facilitator/PayFac model)**
- Partner with providers like Stripe (Stripe Connect), Adyen, or PayPal
- Platform becomes the merchant of record or sub-merchant facilitator
- Fastest path to revenue share on transactions

**2. Traditional Payment Gateway Integration**
- Integrate Square, Braintree, or similar directly
- Simpler but less revenue potential
- Good for MVP/testing before deeper investment

**3. Build Your Own PayFac**
- Highest revenue share, highest complexity
- Requires significant compliance infrastructure
- Only makes sense at scale (usually $50M+ TPV)

## Recommended Path for Most Platforms

**Start with Stripe Connect or similar** because:
- Handles KYC/AML compliance for you
- PCI compliance burden shifts to provider
- Can launch in weeks, not months
- Built-in fraud detection
- Scales with you (can renegotiate rates or move to PayFac later)

## Revenue Models to Consider

| Model | How it Works | Typical Take Rate |
|---|---|---|
| Markup on interchange | Charge users X%, pay provider Y%, keep difference | 0.5-2% |
| Flat fee per transaction | Fixed fee regardless of amount | $0.10-0.50 |
| Subscription + reduced fees | Monthly fee, lower per-transaction cost | Varies |
| Volume-based tiers | Different rates based on transaction volume | 1.5-3.5% |

## Key Implementation Steps

1. **Define your money flow** — Are you facilitating payments between users (marketplace) or collecting payments directly (SaaS billing)?
2. **Choose merchant of record structure** — This affects liability, tax obligations, and dispute handling
3. **Build onboarding flow** — KYC/KYB requirements for sub-merchants if using Connect-style model
4. **Handle payouts** — Timing, methods, currency considerations
5. **Plan for disputes/chargebacks** — Who absorbs risk?
6. **Ensure compliance** — PCI-DSS, state money transmitter laws if applicable

## Questions That Determine Your Best Path

To give you more specific guidance, it would help to know:

- **What type of platform is this?** (Marketplace, SaaS, service booking, etc.)
- **Who initiates payments?** (Your users paying each other, or customers paying your platform directly?)
- **What's your expected transaction volume?**
- **What's your technical team's capacity** for integration work?

Want to share more about your specific platform, and I can suggest a more tailored architecture?

---

Q2: How does payment facilitation as a service work, and how is it different from becoming a fully registered payment facilitator?

# Payment Facilitation: PayFac-as-a-Service vs. Full Registration

## What is Payment Facilitation?

A payment facilitator (PayFac) allows businesses (sub-merchants) to accept payments without needing their own individual merchant account with an acquiring bank. Instead, the PayFac holds the master merchant account and onboards sub-merchants under its umbrella, simplifying and speeding up the process of accepting payments.

## PayFac-as-a-Service (PFaaS)

This is a model where a company partners with an existing infrastructure provider to gain PayFac-like capabilities without building everything from scratch.

**How it works:**
- A software platform (like a SaaS company, marketplace, or vertical-specific platform) partners with a provider that already has PayFac registration, banking relationships, and compliance infrastructure
- The provider handles underwriting, risk management, compliance, settlement, and regulatory relationships
- The platform gets a branded or semi-branded payment experience and often shares in the revenue (interchange, markup)
- Onboarding sub-merchants is faster since the heavy lifting is already built

**Pros:**
- Faster time to market (weeks/months vs. 12-18+ months)
- Lower upfront capital investment
- Reduced compliance burden (PCI DSS, AML/KYC, card network rules)
- No need to build risk/underwriting teams

**Cons:**
- Revenue share with the provider (lower margins than full ownership)
- Less control over underwriting decisions, risk tolerance, and merchant experience
- Dependent on provider's infrastructure and terms

## Fully Registered Payment Facilitator

This means becoming an actual registered PayFac with the card networks (Visa, Mastercard) directly, sponsored by an acquiring bank.

**How it works:**
- The company applies to card networks and secures a sponsoring bank relationship
- Builds (or licenses separately) its own underwriting, KYC/AML, fraud monitoring, and compliance systems
- Takes on direct liability for sub-merchant risk, chargebacks, and regulatory compliance
- Controls the entire merchant lifecycle: onboarding, underwriting, funding, risk decisions

**Pros:**
- Full control over the sub-merchant experience and risk appetite
- Higher revenue capture (no intermediary taking a cut)
- Strategic asset/differentiator for the business
- Flexibility to build custom underwriting rules for niche verticals

**Cons:**
- Significant capital investment (technology, compliance staff, reserves)
- Long approval timelines with card networks and banks
- Ongoing regulatory and compliance liability
- Requires dedicated risk, compliance, and support teams

## Key Differences Summarized

| Aspect | PayFac-as-a-Service | Fully Registered PayFac |
|---|---|---|
| **Time to launch** | Fast (weeks-months) | Slow (12-18+ months) |
| **Cap

---

Q3: What should I look for in an embedded payments provider in terms of onboarding speed, underwriting, and compliance support?

# Evaluating Embedded Payments Providers: Key Criteria

## Onboarding Speed

**What to look for:**
- **Time-to-first-transaction** — ask for actual median/average numbers, not marketing claims. Good providers can quote real data (e.g., "80% of merchants complete onboarding in under 10 minutes")
- **API-driven vs. portal-driven onboarding** — can you embed the merchant application directly into your product, or do you redirect users to a third-party portal?
- **Progressive/staged onboarding** — can merchants start transacting at lower limits while additional verification happens in the background, rather than blocking until everything is complete?
- **Pre-fill and data reuse** — does the provider support pulling data from sources you already have (business registration APIs, Plaid-style bank verification) to reduce manual entry?

**Questions to ask:**
- What's the actual rejection/kickback rate at onboarding, and why do applications get kicked back most often?
- Can I customize the onboarding flow/fields to match my platform's UX?

## Underwriting

**What to look for:**
- **Risk-based tiering** — not all merchants should face the same underwriting bar; look for dynamic risk scoring rather than one-size-fits-all
- **Automated decisioning rate** — what percentage of applications are approved/declined algorithmically vs. requiring manual review?
- **Vertical-specific risk models** — if you're in a higher-risk category (travel, CBD, marketplaces with delayed delivery), does the provider have experience and specific underwriting logic for your space?
- **Transparency into decline reasons** — will the provider give you (and your merchants) actionable reasons for declines, or just a black-box rejection?
- **Ongoing/continuous underwriting** — how do they monitor for risk changes post-onboarding (chargeback spikes, processing volume anomalies) rather than just underwriting at signup?

**Questions to ask:**
- What's your average manual review time when a case is escalated?
- How do you handle merchants who don't fit standard risk profiles (e.g., new businesses, high-ticket items)?
- Who owns the underwriting risk — you, a sponsor bank, or a hybrid model?

## Compliance Support

**What to look for:**
- **Licensing structure** — are they a registered Payment Facilitator (PayFac), PayFac-as-a-Service, or do you need your own PayFac license? This affects your liability and control.
- **KYC/KYB depth** — do they handle beneficial ownership verification, OFAC/sanctions screening, and PEP checks natively, or do you need to bolt on a separate vendor?
- **Card network compliance** — do they manage Visa/Mastercard registration requirements for you (especially if you're a platform enabling sub-merchants)?
- **PCI DSS scope reduction** — how much PCI burden is lifted off your plate (tokenization, hosted fields, etc.)?
- **State money transmitter licensing** — if applicable to your model, who hol

---

Q4: How can a SaaS company offer sub-merchant accounts to its customers without taking on the full risk and regulatory burden of a payment facilitator?

# Sub-Merchant Accounts Without Full PayFac Risk

SaaS companies have several models to offer embedded payments without becoming a fully licensed, fully liable Payment Facilitator (PayFac). Here are the main approaches:

## 1. **PayFac-as-a-Service (Managed PayFac)**

Partner with a provider (Stripe Connect, Adyen for Platforms, Payrix, Finix, Infinicept) that holds the actual PayFac/acquirer relationship and licensing.

- **You get:** Sub-merchant onboarding, branded checkout, faster settlement, revenue share
- **They retain:** Underwriting authority, KYC/AML compliance, card network registration, most regulatory liability
- **You still own:** UX, pricing to sub-merchants, some risk decisioning depending on contract

This is the most common path — you get PayFac-*like* economics and control without becoming the licensed entity.

## 2. **Referral / Reseller Model**

Simplest exposure: you refer customers to a payment processor and earn a commission.

- Processor owns the merchant relationship entirely
- You have minimal integration depth and limited revenue upside
- Lowest risk, lowest control

## 3. **Managed/White-Label Merchant of Record (MoR)**

A third party (like Stripe, Paddle, or a similar MoR) becomes the actual seller of record for transactions.

- They assume chargeback liability, tax remittance, compliance
- Good for marketplaces/subscription products where you don't need granular sub-merchant control
- Less flexible for complex split payments or industry-specific underwriting

## 4. **Sponsor Bank + BIN Sponsorship Partnership**

You contract with a sponsor bank and a processor, taking on more responsibility (underwriting, some KYC) but without becoming a registered PayFac yourself — a hybrid model sometimes called "PayFac Lite."

- Requires more compliance infrastructure than options 1–3
- Still leans on partner's master merchant agreement with card networks

## Key Trade-offs to Evaluate

| Factor | Referral | MoR | Managed PayFac | Full PayFac |
|---|---|---|---|---|
| Integration effort | Low | Medium | Medium-High | High |
| Revenue share retained | Low | Medium | High | Highest |
| Compliance burden | Minimal | Low | Moderate | Full |
| Onboarding control | None | Limited | High | Full |
| Time to launch | Fast | Fast | Moderate | Slow (months) |

## What to Actually Look For in a Partner

- **Underwriting API** — can you influence risk decisions/pass data even if you don't own final approval?
- **Liability allocation in the contract** — who eats chargebacks, fraud losses, reserve requirements?
- **Settlement speed and control** — does it match your business model (e.g., marketplaces needing split payments)?
- **Compliance offloading specifics** — P

---

Q5: What are typical revenue share models when a software company partners with a payments platform to monetize transactions?

# Common Revenue Share Models in Software-Payments Partnerships

When software companies (SaaS platforms, marketplaces, vertical solutions) partner with payment processors to monetize transactions, several models are typical:

## 1. **Basis Points (bps) Revenue Share**
- Software company earns a fixed percentage of transaction volume (e.g., 10-50 bps)
- Simple, predictable, scales with GMV
- Common in payment facilitator (PayFac) models

## 2. **Markup/Spread Model**
- Software company negotiates wholesale processing rate with payment partner
- Charges merchants a marked-up rate
- Keeps the difference (e.g., processor charges 2.5%, platform charges 2.9%, keeps 0.4%)

## 3. **Tiered/Volume-Based Revenue Share**
- Percentage share increases as processing volume grows
- Incentivizes platform to drive adoption
- Example: 15% of net revenue at <$10M volume, 25% at $10-50M, 35% above

## 4. **Per-Transaction Fee Split**
- Fixed dollar amount per transaction split between parties
- Common for platforms with lower-value, high-frequency transactions

## 5. **Hybrid Models**
- Combination of bps + fixed fee (similar to interchange-plus pricing)
- Software company earns share of both components

## 6. **PayFac-as-a-Service Models**
- Software company becomes a sub-merchant facilitator
- Earns larger share (often 50-80% of net revenue) but takes on more risk/compliance burden
- Requires underwriting, KYC, and liability

## Key Variables Affecting Deal Structure:
- **Who owns the merchant relationship** (affects risk allocation)
- **Underwriting responsibility** (platform vs. payment partner)
- **Volume commitments/minimums**
- **Embedded finance features** (lending, cards) often carry different economics
- **Exclusivity clauses** (higher rev share for exclusive processing)

## Typical Economics
- Pure referral models: 10-20% of net revenue
- Managed/embedded payments: 30-50% of net revenue
- Full PayFac with own risk: 60-80%+ of net revenue

Want me to go deeper on any particular model (e.g., PayFac economics, or how embedded lending changes the split)?

Q1: What is the best way for a software platform to add payment processing and start earning revenue from transactions?

Integrating payment processing into a software platform can significantly enhance its functionality and enable revenue generation through transaction fees. Here are the steps and considerations for effectively adding payment processing to your platform:

### 1. **Define Your Revenue Model**
   - **Transaction Fees:** Charge a percentage or a flat fee for each transaction processed.
   - **Subscription Fees:** Consider a subscription model for users who want to access premium features.
   - **Freemium Model:** Offer basic services for free and charge users for advanced features.

### 2. **Choose a Payment Processor**
   - **Popular Options:** Consider established payment processors like Stripe, PayPal, Square, or Braintree, which offer robust APIs and documentation.
   - **Evaluate Costs:** Look at transaction fees, monthly fees, and any hidden costs.
   - **Integration Ease:** Assess how easily the payment processor can be integrated with your platform.

### 3. **Ensure Compliance**
   - **PCI Compliance:** Ensure your platform meets Payment Card Industry Data Security Standards (PCI DSS) requirements.
   - **Regulatory Compliance:** Depending on your location and business model, you may need to adhere to local laws relating to payments and consumer protection.

### 4. **Implement Secure Payment Features**
   - **Tokenization:** Use tokenization to securely store customer payment information.
   - **Fraud Prevention:** Implement mechanisms to detect and prevent fraudulent transactions, such as validation checks and 3DS (Three-Domain Secure).
   - **SSL Certificates:** Make sure your platform uses HTTPS to encrypt data transmission.

### 5. **Integrate Payment API**
   - Utilize the chosen payment processor’s API to integrate payment functionalities into your platform.
   - Provide a smooth user experience for payment processing—minimize the number of steps and ensure the interface is intuitive.

### 6. **Test the Payment Process**
   - Conduct extensive testing to ensure the payment flow is seamless and works as expected. Test various scenarios, including successful payments, declined transactions, refunds, and chargebacks.

### 7. **Launch and Monitor**
   - Roll out the payment features to your users and monitor performance closely for any issues or user feedback.
   - Track transaction volumes, failure rates, and other metrics to optimize the payment process over time.

### 8. **Provide Support and Resources**
   - Offer customer support for payment-related inquiries.
   - Create documentation or FAQs to assist users with common payment issues.

### 9. **Market Your Payment Solution**
   - Promote the newly added payment features to your existing user base and potential customers. Emphasize any benefits like lower fees or faster processing times compared to competitors.

### 10. **Iterate and Improve**
   - Gather feedback and user data to continually refine the payment process and offer new features that meet customer needs.

### Additional Considerations
- **International Payments:** If your platform targets users globally, choose a payment processor that supports multiple currencies and countries.
- **Mobile Optimization:** Ensure the payment interface is optimized for mobile devices, as many transactions may occur via smartphones.
- **User Experience:** Strive for a seamless and frictionless payment experience to reduce cart abandonment and enhance user satisfaction.

By following these steps and ensuring compliance and security, your software platform can effectively integrate payment processing and start generating revenue from transactions.

---

Q2: How does payment facilitation as a service work, and how is it different from becoming a fully registered payment facilitator?

Payment facilitation as a service (PFaaS) and becoming a fully registered payment facilitator (PF) are two different approaches to handling payments for merchants and businesses. Here’s an overview of each and the key differences between them:

### Payment Facilitation as a Service (PFaaS)

**Overview:**
PFaaS refers to a model where a company provides payment facilitation services to other businesses without assuming full responsibility for the payment processing. In this model, the service provider typically partners with existing payment processors or banks to offer a solution that allows merchants to accept payments seamlessly.

**How It Works:**
1. **Integration:** The PFaaS provider integrates payment processing capabilities into their platform, enabling merchants to accept payments through various methods (credit/debit cards, mobile payments, etc.).
2. **Onboarding:** Merchants are onboarded through the PFaaS provider’s platform, usually with a simplified process compared to traditional merchant accounts.
3. **Compliance and Risk Management:** The PFaaS provider handles compliance, underwriting, fraud detection, and other risk management aspects on behalf of the merchants.
4. **Fees:** Merchants are charged fees for payment processing, which are typically bundled into the service agreement.

**Characteristics:**
- Lower regulatory burden for merchants.
- Quick onboarding process.
- The PFaaS provider generally does not take on the full responsibilities of a payment facilitator.

### Fully Registered Payment Facilitator

**Overview:**
A fully registered payment facilitator is a company that has obtained the necessary licenses and registrations to underwrite merchants directly, allowing them to facilitate payments independently. This is a more comprehensive and complex setup compared to PFaaS.

**How It Works:**
1. **Acquiring Bank Partnership:** The PF partners with an acquiring bank to be able to process credit card transactions and manage merchant accounts.
2. **Merchant Underwriting:** The PF is responsible for the underwriting process for the merchants it onboard, assessing their risk and ensuring compliance with payment industry regulations.
3. **Compliance:** Fully Registered PFs must ensure compliance with various financial regulations and standards, such as PCI DSS (Payment Card Industry Data Security Standard).
4. **Settlement:** They handle funds settlement, merchant payouts, chargebacks, and transaction dispute management.

**Characteristics:**
- Full responsibility for managing merchant relationships.
- Greater regulatory and compliance obligations.
- Ability to provide customized merchant services.

### Key Differences

1. **Regulatory Burden:**
   - PFaaS has a lower regulatory burden since it operates under the umbrella of a larger payment processor or bank.
   - A fully registered PF must take on all the regulatory and compliance responsibilities and must be fully compliant with PCI, KYC (Know Your Customer), and other relevant regulations.

2. **Merchant Onboarding:**
   - PFaaS typically has a simplified onboarding process, making it easier for small to medium-sized businesses.
   - Fully registered PFs often have comprehensive underwriting processes reflective of taking on significant risk.

3. **Risk Management:**
   - PFaaS providers typically manage risk on a more limited scale and often outsource some functions to payment processors.
   - Fully registered PFs must implement their own risk management systems and strategies.

4. **Revenue Model:**
   - PFaaS may charge a service fee or a percentage of transactions.
   - Fully registered PFs set their pricing models, which can vary based on the services offered and the merchants' profiles.

In summary, PFaaS offers a more accessible, lower-risk solution for businesses looking for payment processing capabilities without delving into the complexities of becoming a fully regulated payment facilitator, which requires extensive resources and regulatory compliance.

---

Q3: What should I look for in an embedded payments provider in terms of onboarding speed, underwriting, and compliance support?

When evaluating an embedded payments provider, particularly with respect to onboarding speed, underwriting, and compliance support, consider the following aspects:

### Onboarding Speed

1. **Streamlined Processes:**
   - Look for providers that offer a seamless and intuitive onboarding process, minimizing friction and maximizing speed.
   - Automated verification and setup can significantly reduce onboarding time.

2. **Integration Ease:**
   - Check if the provider offers robust APIs and SDKs that facilitate easy integration with your existing systems.
   - Evaluate the availability of pre-built connectors for common platforms/software.

3. **Documentation and Support:**
   - Comprehensive documentation and strong customer support can expedite the onboarding process.
   - Look for providers that provide technical support during the integration phase.

### Underwriting

1. **Automated Underwriting:**
   - Providers that utilize automated underwriting algorithms can often speed up the approval process for merchants by quickly analyzing risk and creditworthiness.

2. **Flexible Criteria:**
   - Understand the underwriting criteria and assess if it is flexible enough to cater to different business models and risk profiles.
   - Look for providers that assess not only credit scores but also business activity and transaction history.

3. **Speed of Decisions:**
   - Inquire about the average time taken for underwriting decisions. A faster decision process can significantly impact your go-to-market strategy.

### Compliance Support

1. **Regulatory Expertise:**
   - Ensure the provider has a strong understanding of the regulatory landscape relevant to your industry and geography (e.g., PCI-DSS, AML/KYC regulations).
   - They should be capable of guiding you through compliance requirements and changes in regulations.

2. **Ongoing Compliance Monitoring:**
   - Look for compliance support that extends beyond onboarding, including ongoing monitoring and support for audits.
   - Consider whether they offer tools or services for continuous compliance management.

3. **Risk Management Tools:**
   - Some providers offer risk management and fraud detection tools. Assess how these tools integrate into their compliance framework and how they can help you manage potential risks.

### Additional Considerations

1. **Reputation and Reviews:**
   - Research the provider’s reputation in the industry, including reviews from other businesses who have used their services.

2. **Scalability:**
   - Consider whether the provider can scale with your growth. This includes the capability to handle increasing transaction volumes and expanding to new markets.

3. **Fees and Pricing Structure:**
   - Understand any fees associated with onboarding, transaction processing, or compliance, and assess their alignment with your budget and business model.

By thoroughly evaluating these aspects, you can find an embedded payments provider that aligns with your business needs and supports your growth effectively.

---

Q4: How can a SaaS company offer sub-merchant accounts to its customers without taking on the full risk and regulatory burden of a payment facilitator?

A Software as a Service (SaaS) company can explore several strategies to offer sub-merchant accounts to its customers without fully assuming the risks and regulatory burdens typically associated with being a payment facilitator. Here are some potential approaches:

1. **Partner with a Payment Facilitator (PayFac):** Collaborate with an established payment facilitator that has the regulatory framework in place. Your SaaS platform can integrate their services, allowing your customers to create sub-merchant accounts under the PayFac's umbrella. You'll need to establish a clear partnership agreement outlining revenue sharing, compliance responsibilities, and support.

2. **Use a Payment Gateway with Sub-Merchant Capabilities:** Some payment gateways offer sub-merchant capabilities without the full obligations of a PayFac. This model allows your customers to accept payments under your account, with the gateway managing compliance and risk. Choose partners that provide robust APIs for easy integration.

3. **Merchant of Record (MoR) Model:** In this approach, your company acts as the merchant of record for transactions, while the actual selling entities are the sub-merchants. You handle payment processing and retain compliance responsibilities, but you can transfer certain risks to a third-party provider, such as a funder or a compliance expert, to alleviate the burden.

4. **Leverage Third-Party Compliance Solutions:** Utilize third-party services that specialize in payment compliance and risk management. You can outsource aspects of compliance, allowing your SaaS business to provide sub-merchant accounts while minimizing the complexity of regulatory adherence.

5. **Provide Payment Solutions as an Integrator or Marketplace:** Rather than owning the payment processing vertically, provide integration with various payment solutions that facilitate transactions. By directing your customers toward multiple payment options, you reduce your liability and responsibility for compliance.

6. **Educate and Equip Customers for Compliance:** Offer tools, resources, and documentation to help your customers navigate compliance requirements themselves. By empowering them with knowledge, you position your SaaS as a supportive partner rather than a facilitator.

7. **Limit Scope of Services:** Offer a narrow scope of payment-related services that places less risk on your company. For example, providing tools for invoicing or recurring billing without directly managing transaction funds can keep you compliant while offering value associated with payment processing.

8. **Implement Strong Due Diligence:** If you decide to provide some level of merchant account services, ensure that you have comprehensive due diligence processes in place for onboarding sub-merchants. Know Your Customer (KYC) processes can mitigate risks without taking on full regulatory liabilities.

9. **Consider an LLC or Partnership Structure:** Depending on your jurisdiction, you might explore forming an LLC or another partnership structure with the payment processor. This structure can clarify the limits of liability and responsibility for compliance matters.

10. **Regular Legal Consultation:** Consult with legal experts specializing in financial regulations to ensure that any agreements or solutions you pursue maintain compliance with all applicable laws and standards, reducing your risks.

By combining these strategies, a SaaS company can provide sub-merchant accounts to its customers in a way that protects itself from significant regulatory risks while still offering valuable payment processing capabilities.

---

Q5: What are typical revenue share models when a software company partners with a payments platform to monetize transactions?

When a software company partners with a payments platform to monetize transactions, several typical revenue share models can be employed. These models dictate how revenue generated from transactions is divided between the two parties involved. Here are some common revenue share structures:

1. **Percentage of Transaction Fee**:
   - **Revenue Share Percentage**: The payments platform takes a percentage of each transaction processed. The software company receives the remaining percentage. For example, if a transaction fee is 3%, the payment platform might keep 1.5% while giving the software company 1.5%.
   - **Tiered Plans**: Some agreements may have tiered percentages based on transaction volume, where higher volumes trigger lower fees.

2. **Flat Fee Per Transaction**:
   - The payments platform charges a flat fee for each transaction processed, separate from the percentage take. The software company retains the rest. For instance, if the platform charges $0.30 per transaction, the software company keeps the remaining amount.

3. **Revenue Sharing by Product or Service**:
   - Different products or services might have varying revenue share agreements. For example, digital goods might have a different model than physical goods or subscriptions.

4. **Subscription Model**:
   - If the software company operates on a SaaS (Software as a Service) model, the payments platform might charge a subscription fee or a minimum monthly fee based on expected transaction volume, in addition to the transaction service fees.

5. **Hybrid Models**:
   - A combination of percentage and flat fees may be used. The payment platform might charge a percentage for larger transactions and a flat fee for smaller ones, balancing revenue based on transaction amounts.

6. **Performance-Based Incentives**:
   - The revenue share can be connected to performance metrics, such as user growth or the volume of transactions. For example, a higher transaction volume might qualify the software company for a lower percentage on fees.

7. **Cross-Promotion and Marketing Agreements**:
   - In addition to transaction fees, the agreement may include elements where the payments platform promotes the software company or vice versa, with additional revenue provisions based on successful leads generated through marketing efforts.

8. **Minimum Revenue Guarantee**:
   - The payments platform may offer a minimum revenue guarantee to the software company, ensuring that even if transaction volumes are low, the software company receives a set amount.

9. **Cost-Plus Model**:
   - In some partnerships, the payments platform may charge the software company its costs plus a markup, which can be negotiated as a revenue share rather than a straightforward commission.

10. **Equity Options**:
    - In some cases, instead of a traditional revenue share, the payments platform might negotiate for equity in the software company. This aligns incentives but carries higher risk for the payments platform.

The choice of model depends on various factors, including the type of services offered, target market, volume of anticipated transactions, and the relationship dynamics between the software company and the payments platform. Successful partnerships often involve a flexible approach that can be adjusted based on the evolving needs and performance of both parties.

Q1: What is the best way for a software platform to add payment processing and start earning revenue from transactions?

The best way for a software platform to add payment processing and start earning revenue is to **integrate a platform-specific payment infrastructure provider** (such as **Stripe Connect**, **Finix**, or **Braintree**) rather than building a custom gateway or using a standard merchant-only processor.

This approach allows the platform to legally and technically **embed payments** for its merchants or users, enabling the platform to automatically **split fees**, manage **sub-merchant onboarding**, and earn revenue via **transaction fees** or **markup** without assuming the full burden of financial compliance[6].

### Why Infrastructure Providers Are Superior for Platforms
Standard processors like PayPal or Square advertised for general e-commerce are often insufficient for platforms because they lack **platform-level infrastructure** needed to manage multiple merchants[6]. Infrastructure providers specifically handle:
*   **Sub-merchant management:** Registering and onboarding your users as distinct merchants under your platform[6].
*   **Compliance and underwriting:** The provider assumes the regulatory risk (PCI DSS, KYC) rather than the platform building it from scratch[6][4].
*   **Revenue sharing:** Built-in tools to automatically split transaction fees between the platform and the merchant[6].

### Top Recommended Solutions
| Provider | Best For | Key Advantage |
| :--- | :--- | :--- |
| **Stripe Connect** | Speed and simplicity | Valid starting point if **speed is the priority**; offers ready-to-use APIs for rapid integration[6]. |
| **Finix** | Long-term scale | Purpose-built for platforms; handles **compliance, underwriting, and sub-merchant management directly**[6]. |
| **Braintree** | PayPal adoption | Ideal for platforms where **users already prefer PayPal**[6]. |
| **WePay** | Chase banking relationships | Recommended if a **Chase commercial relationship** is a strict requirement[6]. |

### Why You Should Not Build Your Own Gateway
Building a custom payment gateway is a **complex task** requiring significant investment in time, resources, and technical expertise[4].
*   **Compliance Burden:** You must obtain **PCI DSS certifications** and regularly audit systems to protect sensitive data[4].
*   **Bank Partnerships:** You must negotiate lengthy contracts with **banks and credit card companies** to route transactions[4].
*   **Development Time:** Developing the software alone can take **6 to 12 months**, delaying revenue generation[4].
*   **Expert Warning:** Industry experts strongly advise **not to "roll your own"** if you are starting with basic resources, as the security and operational mess is overwhelming[1].

### Implementation Steps to Start Earning Revenue
1.  **Select an Infrastructure Provider:** Choose **Stripe Connect** for speed or **Finix** for a dedicated platform infrastructure[6].
2.  **Integrate the API:** Use the provider's **ready-to-use APIs** to enable merchants to accept payments directly on your platform[2].
3.  **Configure Fee Splitting:** Set up the logic to automatically deduct your platform fee and remit the remainder to the merchant[6].
4.  **Automate Data Flow:** Use integration tools (like **Albato** or **Zapier**) to push transaction data to your CRM or accounting software for real-time reporting[3][8].

By using this model, the platform can start earning revenue **as soon as possible** without spending months or years on a from-scratch project[5].

---

Q2: How does payment facilitation as a service work, and how is it different from becoming a fully registered payment facilitator?

**Payment Facilitation as a Service (PayFac-as-a-Service)** works by allowing a software platform to act as a **sub-payment facilitator** under an existing, fully registered PayFac’s **master merchant account**, enabling instant onboarding of end users and monetization of payments without bearing regulatory or infrastructure costs[1][2]. In contrast, becoming a **fully registered payment facilitator** requires the business to become the **merchant of record**, assume full liability for transaction risk, and independently manage compliance, underwriting, and technology infrastructure[3][8].

### How PayFac-as-a-Service Works
In this model, the software platform integrates with a registered PayFac provider (e.g., Usio, Paysafe) via API, and its customers are onboarded as **sub-merchants** under the provider’s sponsorship[2][5].
*   **Instant Onboarding:** End users complete a simplified application and can accept credit, debit, and ACH payments within minutes, often with same-day approval[1][6].
*   **Revenue Model:** The platform earns revenue from the **spread** between the buy rate (from processing networks) and the sell rate charged to the end customer[1].
*   **Shared Responsibility:** The registered PayFac provider handles the "heavy lifting," including **compliance**, **risk management**, **fraud detection**, and **transaction processing**, while the platform focuses on its core business[2][9].
*   **Reduced Barriers:** The onboarding process involves a partnership agreement and minimal documentation (e.g., no bank statements required), significantly expediting setup compared to the traditional model[2].

### Key Differences: PayFac-as-a-Service vs. Fully Registered PayFac

| Feature | PayFac-as-a-Service (Sub-PayFac) | Fully Registered PayFac (Master Merchant) |
| :--- | :--- | :--- |
| **Merchant Status** | Acts as a **sub-entity** under a master account[1][2] | Acts as the **merchant of record** (master merchant)[3][8] |
| **Risk & Liability** | **Low risk**; the sponsor PayFac assumes transaction and compliance risk[2][9] | **Full risk**; the PayFac assumes all underwriting, fraud, and financial risk[3][8] |
| **Compliance** | Provider handles **regulatory compliance** and audits[2][9] | PayFac must manage **all compliance**, registration, and oversight independently[7] |
| **Infrastructure** | **Renting** infrastructure (API integration); no need to build systems[5] | **Building** infrastructure (technology, processes, support) from scratch[6][7] |
| **Onboarding Complexity** | **Streamlined**; minimal documentation, partnership agreement[2] | **Complex**; requires sponsor bank approval, significant operational resources, and registration with governing entities[7] |
| **Time to Market** | **Fast**; weeks to months via white-labeling[6] | **Slow**; months to years for setup and approval[7] |

### Why the Distinction Matters
Becoming a fully registered PayFac is akin to **building a highway system**, requiring substantial investment in technology, legal registration, and operational posture to satisfy sponsor banks and card networks[5][7]. PayFac-as-a-Service is like **renting the infrastructure**, allowing companies to monetize payments and offer embedded finance immediately without the "regulatory weight" of being the merchant of record[5]. For businesses without resources to manage risk or compliance, the service model provides the benefits of payment facilitation while avoiding the complexities of full registration[2].

---

Q3: What should I look for in an embedded payments provider in terms of onboarding speed, underwriting, and compliance support?

When evaluating an embedded payments provider, look for **phased onboarding** to enable merchants to go live in hours, **rules-based underwriting** that automates approvals using KYC/KYB data, and **built-in compliance infrastructure** (including AML and KYC) that scales with your volume rather than requiring manual intervention.

### Onboarding Speed
*   **Phased or "Instant" Activation:** The provider should allow merchants to start transacting quickly with minimal checks, layering in full KYC only when required (e.g., for higher transaction volumes) [4]. This avoids the trade-off between "instant activation" and "weeks of compliance checks" [4].
*   **Customizable UX & APIs:** Look for API-driven tools that let you customize the onboarding flow to match your branding and reduce friction, directly impacting merchant activation rates [1][3].
*   **Global Efficiency:** The provider should simplify onboarding globally, handling identity verification efficiently regardless of the merchant's location [1].

### Underwriting Capabilities
*   **Rules-Based Automation:** The provider must support **rules-based underwriting** where you can easily send KYC/KYB data to trigger automated approvals, getting customers onboarded quickly without manual review bottlenecks [1].
*   **End-to-End Flow Evaluation:** Don't just review API documentation; evaluate the entire KYC/KYB flow to ensure it minimizes friction for sub-merchants [7].
*   **Risk Control Logic:** The platform should offer **custom compliance logic** to control risk and flows in ways that reflect your specific user base and business model, rather than using generic third-party rules [4].

### Compliance Support
*   **Built-In Regulatory Infrastructure:** Prioritize providers with a **compliance-first environment** that includes built-in AML and KYC infrastructure, reducing your operational friction and regulatory burden [5].
*   **Multi-Source Transparency:** Check if the provider relies on one or multiple third parties for KYC/KYB checks; a single, integrated source is often more reliable for scaling [3].
*   **Scalable Workflows:** Ensure the provider offers compliance workflows that can scale with your volume and evolving regulations, particularly if you operate across borders or in the EU [4][5].
*   **Full Regulatory Coverage:** The partner should manage the full regulatory burden, including identity verification, transaction monitoring, and card brand mandates, so you don't need to hire specialist compliance staff [1][7][10].

### Key Trade-off to Avoid
Be wary of providers that force you to choose between **fast onboarding** and **deep compliance**. The ideal provider offers both by using phased onboarding to balance speed with necessary regulatory safeguards [4].

---

Q4: How can a SaaS company offer sub-merchant accounts to its customers without taking on the full risk and regulatory burden of a payment facilitator?

A SaaS company can offer sub-merchant accounts without assuming the full risk and regulatory burden of a Payment Facilitator (PayFac) by partnering with a **PayFac-as-a-Service** provider or a **regulated payments infrastructure** platform that acts as the "merchant of record."

In this model, the third-party partner (such as Finix, Skaleet, or a dedicated PayFac provider) retains legal responsibility for compliance, underwriting, and transaction risk, while the SaaS provider retains control over pricing and customer relationships [8][9].

### Key Strategies and Models

| Strategy | How It Works | Risk & Regulatory Outcome |
| :--- | :--- | :--- |
| **PayFac-as-a-Service** | The SaaS partners with an existing PayFac (e.g., an ISO or payment company) that has already completed regulatory registration. The partner boards the SaaS’s customers as sub-merchants under their own umbrella [8]. | The **sponsoring PayFac assumes the risk** for fraud, chargebacks, and funds. The SaaS avoids registering as a PayFac and bypasses direct KYC/AML regulatory duties [8]. |
| **Regulated Infrastructure (e.g., Finix)** | The SaaS uses a specialized infrastructure provider that manages the sponsor bank relationships, compliance, underwriting, and risk monitoring as part of the platform service [9]. | The provider **manages liability** at the infrastructure level, allowing the SaaS to generate revenue without absorbing "fintech-level liability" [9]. |
| **Integrated Payment Partner (e.g., Zift, WePay)** | The SaaS integrates with a payment service provider specifically built for software platforms that offers PayFac-specific tools and APIs [7]. | The partner handles the **technical and risk logic** (fraud monitoring, OFAC screening), removing the need for the SaaS to build its own risk engine [7]. |

### What the SaaS Provider Still Retains
While the partner handles the heavy regulatory lifting, the SaaS company maintains:
*   **Pricing Control:** The ability to set transaction fees and mark up rates [8][9].
*   **Customer Relationships:** Direct management of sub-merchant onboarding and support [9].
*   **Revenue Share:** The ability to monetize payments and keep a portion of the processing revenue [8][9].

### Important Trade-off
The primary downside is that the sponsoring PayFac frequently charges **higher transaction rates** for the sub-merchants to offset the added risk they are absorbing [8]. The SaaS must decide if the speed of onboarding and reduced regulatory burden outweighs the potential increase in customer costs compared to a traditional merchant account model.

---

Q5: What are typical revenue share models when a software company partners with a payments platform to monetize transactions?

Typical revenue share models when a software company (SaaS) partners with a payments platform generally fall into three categories: **flat revenue share**, **markup (spread) models**, and **tiered or value-based share**, where the software company earns a percentage of the **margin** (the difference between the merchant fee and the underlying interchange/processor costs).

### Core Models

| Model Type | How It Works | Typical Range |
|------------|--------------|---------------|
| **Flat Revenue Share** | The payment provider gives the SaaS company a fixed percentage (e.,g., 0.4% or 40–50 basis points) of every transaction processed [6]. | 20–60 basis points (0.2%–0.6%) per transaction [6] |
| **Markup Model** | The SaaS company sets its own merchant fee above the provider’s "buy rate" and keeps the difference as margin [6][7]. The provider may then split this margin (e.g., 50/50) [2]. | SaaS sets markup; margin split often 50/50 above interchange [2] |
| **Tiered / Value-Based Share** | The revenue share percentage increases as merchants process more volume or activate value-added services (e.g., fraud protection, digital invoicing) [4][6]. | Varies by package; can reach up to 90–100% of payment revenue in rare cases [7] |

### Key Mechanics

- **Margin Definition**: Revenue share is typically calculated on the **profit margin** after subtracting interchange fees and processor costs from the total merchant fee [1][2].
- **Example Breakdown**: If the available margin is ~0.6% + $0.10, a 50% split yields ~0.3% + $0.05 for the platform [1].
- **Pricing Control**: In "true" revenue share models (like Fiska), the SaaS company controls its markup above interchange, and the provider splits the difference [2].
- **Risk & Compliance**: Referral/partner models (revenue share) off-load compliance risk to the payment provider but earn less per transaction than full markup models [8].

### Strategic Variations

- **Value-Based Tiering**: Modern programs reward partners not just for volume, but for **merchant adoption depth**—e.g., higher splits if merchants use integrated fraud tools or issue invoices [4].
- **Package-Based Splits**: Some PayFac-as-a-service providers (e.g., Tilled) vary the margin split based on the chosen package, volume, and risk level [2].
- **Usage-Based Classification**: This revenue is often categorized as **usage-based income** rather than recurring MRR, though it becomes predictable as volume stabilizes [6].

These models allow SaaS platforms to monetize transaction volume directly, turning payment processing into a scalable income stream that grows with user economic activity [1]. Up to 60% of total revenue for platforms like Bill.com and AvidXchange comes from payments rather than software fees [6].