Marketplaces and Vendor Payouts (Centralized Payment Model)

⏱️ TL;DR

• Does Memberstack support Stripe Connect? No. Memberstack does not natively support multi-party checkouts, split payments, or onboarding third-party sellers (vendors) to their own Stripe accounts.
• The Workaround: Use the Centralized Payment Model. You collect 100% of the customer payments into your platform's central Stripe account. You then track what you owe vendors in Memberstack (using custom fields) and automate payouts using Zapier/Make combined with a payout provider (like PayPal, Wise, or Trolley).
• Tax Warning: Because you are collecting all the money directly, you are the Merchant of Record. You must handle tax reporting (like 1099s in the US) manually or via a third-party tool, as Stripe Connect's automatic tax features will not apply.

1. Why Memberstack Doesn't Support Stripe Connect

Stripe Connect is Stripe's product for marketplaces (like Airbnb or Etsy) where buyers pay sellers directly, and the platform takes a cut (split payments).

Memberstack is designed for single-merchant billing. When you connect Stripe to Memberstack, all transactions flow directly into your single, primary Stripe account. There is no native way to dynamically split a payment at checkout or route a customer's payment to a specific vendor's Stripe account.

If you are building a marketplace, you must use the Centralized Payment Model detailed below.

2. The Centralized Payment Marketplace Pattern

In this pattern, your platform acts as the middleman for all transactions and manually or semi-automatically distributes earnings to your vendors.

Step 1: Collecting Payments

When a buyer purchases a digital product, subscription, or service on your site, they use standard Memberstack checkout buttons linked to your central Stripe account.

• You can use Memberstack Data Tables or custom fields to link the purchase to a specific Vendor ID so you know who sold what.

Step 2: Vendor Onboarding & Tracking in Memberstack

Your vendors are registered as standard Memberstack members. To pay them, you need to collect their payout details.

Create custom member fields in Memberstack for non-sensitive identifiers, such as:

• Vendor Payout Email (for PayPal or Wise)
• Vendor ID (to match them to your database)

Security Warning: Never store highly sensitive financial information, such as raw bank account numbers, routing numbers, or social security numbers, in Memberstack custom fields. Memberstack custom fields are accessible on the client-side (front-end) to the logged-in member. Storing sensitive financial details here exposes them to security risks. Instead, use a secure third-party payout provider (like Trolley) that securely collects and stores bank details on their own servers, or route this sensitive data directly to a secure, encrypted backend database.

Create a secure Vendor Dashboard page on your site where vendors can manage their profile and access the secure portal of your chosen payout provider to input their banking details.

Step 3: Automating Payouts (The Integration Flow)

You do not want to manually send bank transfers every time a sale is made. Instead, use an automation tool like Make or Zapier to handle payouts on a schedule (e.g., weekly or monthly).

Example Automation Flow:

1. Trigger: A new successful payment is processed in Stripe.
2. Action (Look up): Find the Memberstack member (the Vendor) associated with the sold item.
3. Action (Calculate): Use Zapier/Make to calculate the split. For example, if the sale was $100 and your platform fee is 20%, calculate the vendor payout as $80.
4. Action (Log): Log this $80 credit in a database (like Airtable, Google Sheets, or Memberstack Data Tables) as a "Pending Payout".
5. Action (Payout Trigger): At the end of the month, run a secondary scenario that rolls up all "Pending Payouts" and sends a bulk payout command to your payout provider.

3. Recommended Payout Providers

Because you cannot use Stripe Connect to pay out vendors, you will need to use an API-driven payout service. Here are the best options for centralized marketplaces:

4. Crucial Tax & Compliance Notes

When using Stripe Connect, Stripe handles tax verification (W-8/W-9 forms) and automatically issues 1099-K forms to your vendors.

With the Centralized Payment Model, you lose this automation.

• Merchant of Record: Because 100% of the revenue hits your bank account first, tax authorities (like the IRS) view this as your revenue.
• W-9/W-8 Collection: You are legally required to collect tax information from your vendors before paying them.
• 1099 Reporting: If a US-based vendor earns over $600 on your platform in a calendar year, you are responsible for filing and sending them a 1099-NEC or 1099-MISC form.
• Pro-Tip: If your marketplace scales, we highly recommend using Trolley or Tax1099 integrated with your payout automation to collect tax forms and automate this reporting.

❓ Frequently Asked Questions (FAQ)

Q: Can vendors log in to see their sales history?

Yes. You can use Memberstack's native Data Tables to store and display transaction data directly in your app. Alternatively, if you use an external database like Airtable, you can sync your data to Webflow using a two-way syncing tool like Whalesync (which features a dedicated Memberstack integration template). This allows you to dynamically display a custom list of sales, earnings, and payout history directly on their logged-in Vendor Dashboard. 

Q: Can I use Stripe Payment Links for my vendors?

No. Stripe Payment Links are tied to your primary Stripe account. If a vendor wants to use their own Stripe account to collect payments directly, they cannot do so through your Memberstack integration.

Q: Is there an official Memberstack template for marketplaces?

We do not have a native marketplace template because of the external automation required. However, many customers successfully run directories and marketplaces by pairing Memberstack (for user authentication) with Webflow, Airtable, and Make.