thelastapi
Get started free

Merchant of record vs payment processor for a small SaaS

A merchant of record acts as the legal seller for your software, while a payment processor simply routes card charges through your own company entity.

On this page 7 sections

A payment processor only routes card transactions into your own merchant account, whereas a merchant of record acts as the legal seller of your software and handles the underlying transaction liability. When you use a payment processor directly, you must register a corporate entity, pass bank underwriting, set up merchant accounts, and configure global sales tax before you can take your first payment. When you sell through a merchant of record, the provider sells to the customer on your behalf, which allows you to start charging for software the moment your code is written.

Understanding the operational differences between these two models helps you pick the right setup for an early SaaS product, prototype, or new project.

The core distinction is which business entity signs the transaction and faces the buyer's financial institution.

With a pure payment processor:

  • You are the merchant. Your company's legal name, tax identification number, and bank accounts are tied directly to the processing infrastructure.
  • You undergo underwriting first. Before taking live payments, you must provide personal identification, business registration papers, and bank details.
  • You handle card compliance. You are responsible for dispute handling, international charge rules, and tax compliance across every country where you sell.

With a merchant of record:

  • The platform is the merchant. The platform's corporate entity executes the sale. On customer credit card statements, the charge appears with the platform's descriptor and your custom suffix (for example, VIBIZ, INC* <SUFFIX>).
  • You can launch immediately. You do not need to submit business paperwork or personal identification before running your first live transaction.
  • Identity checks happen at payout. You can test market demand, sell subscriptions, and accrue revenue in your project balance immediately. You only complete an identity check and link a bank account when you are ready to withdraw your earnings.

For an early-stage tool, this distinction removes several days of administrative delays. You can read more about starting out without corporate underwriting in our guide to taking payments online without opening a merchant account.

How the two models compare for a small SaaS

Here is how the responsibilities, costs, and timelines break down between using thelastapi as your merchant of record versus connecting your own merchant account:

FeatureMerchant of record (thelastapi default)Direct payment processor (own account)
Merchant of recordthelastapi (VIBIZ, INC* <APP>)Your business entity
Setup timeImmediate (available on project creation)Requires account approval and underwriting
Upfront identity checkNone (required only at withdrawal)Required before taking live transactions
Base card fee2.9% + 30¢ per payment (most US cards)Determined by your processor contract
Platform fee200 bps (2%)Retains fees.own_account_bps application fee
Dispute feeDisputed amount + $15Determined by your processor
Payout hold7 days on live payments (0 days in test mode)Direct processor payout schedule
Currencies supported35 currencies (balance settled in USD)Determined by your processor
Withdrawal destinationUS, Canada, UK, EEA, and SwitzerlandDetermined by your bank relationship

On a $100 sale with the standard merchant setup, card processing takes $3.20 and the platform fee takes $2.00, depositing $94.80 into your project balance. Full fee breakdowns are explained in Payments: how money moves.

Setting up a SaaS checkout in code

Using a merchant of record lets you configure products and checkouts without managing API secrets for third-party processors. In thelastapi, payments work with a single project environment variable: VIBIZ_APP_KEY.

First, add a subscription product using the CLI:

Terminal
vibiz payments products add Pro --amount 1500 --interval month --lookup-key pro-monthly --dev

To create a checkout session inside a Next.js application, install @vibiz/app and redirect the buyer to the hosted checkout page:

TypeScript
import { redirect } from 'next/navigation';
import { vibiz } from '@vibiz/app';

export async function upgrade(userId: string) {
  const { url } = await vibiz.payments.checkout({
    lookup_key: 'pro-monthly',
    user: userId,
    success_url: 'https://example.com/billing/success',
    cancel_url: 'https://example.com/pricing',
  });

  redirect(url);
}

The checkout page is generated specifically for that single buyer and expires after one hour. You can brand this page to match your SaaS by supplying your logo, button color, and font choices via the API or CLI flags. Read our complete walkthrough on how to add a subscription checkout to a SaaS for details on managing active plan status.

Managing payouts, balances, and currencies

When running through a merchant of record, incoming funds are tracked on the platform's internal ledger.

Settlement and holds

Live payments remain pending for a hold period of 7 days (fees.hold_days) before becoming available for withdrawal. In the development environment, there is no hold period.

If you charge customers across borders, you can accept payments in 35 different currencies (such as eur, gbp, cad, jpy, and aud). Regardless of the currency charged, the project balance is maintained in USD. Transactions are converted at the processor's daily rate minus standard currency conversion fees (typically 1–2%). The payment object retains both amount_cents in the billed currency and settled_usd_cents in USD.

Withdrawing funds

When you are ready to withdraw your available balance:

  1. Verify your identity once. In the console under Payments ▸ Get paid, complete the embedded identity form and add your bank routing and account numbers. thelastapi never stores your tax ID or bank credentials. Supported payout destinations include the US, Canada, the UK, Switzerland, and the EEA.
  2. Execute the withdrawal. Trigger the payout from the dashboard or through the CLI:
Terminal
vibiz payments withdraw

If your account experiences refunds or disputes exceeding your total earnings, the balance becomes negative, which temporarily pauses withdrawals until future sales cover the deficit.

Handling webhook notifications

Because billing events happen asynchronously, your SaaS application needs an endpoint to handle successful charges, subscription cancellations, and failed renewals.

When thelastapi acts as the merchant, webhooks can be verified automatically using your existing VIBIZ_APP_KEY. Create a route handler in your application at /api/vibiz/webhook:

TypeScript
import { vibiz } from '@vibiz/app';

export async function POST(req: Request) {
  let event;
  try {
    event = await vibiz.webhooks.receive(req);
  } catch {
    return new Response('bad signature', { status: 400 });
  }

  switch (event.type) {
    case 'payment.succeeded':
      // Access event.data.object.user and event.data.object.amount_cents
      break;
    case 'subscription.created':
    case 'subscription.canceled':
      // Update the user's access level in your database
      break;
    case 'invoice.payment_failed':
      // Alert the customer that their payment method failed
      break;
  }

  return new Response('ok');
}

Because delivery retries occur over three days if your endpoint times out or returns a non-2xx status, your webhook handlers should always deduplicate events using event.id. To dive deeper into payload signatures and testing, see how to verify payment webhooks safely.

When should you connect your own processor account?

Starting with a merchant of record is ideal when building a prototype, launching an MVP, or operating without an established corporate entity. However, as transaction volume scales, you may want direct bank payouts or custom processor arrangements.

thelastapi allows projects to connect their own processor account whenever needed:

Terminal
vibiz payments connect

This command generates a secure onboarding link for the project owner. Once connected:

  • Future sales process directly on your own merchant account.
  • Funds bypass the 7-day platform hold and pay out on your processor's standard schedule.
  • thelastapi retains an application fee (fees.own_account_bps) on each sale.
  • Existing balances accumulated under the merchant of record remain in your platform ledger and can be withdrawn normally.
  • Your app's code (@vibiz/app checkouts, subscription checks, and webhooks) requires zero changes.

Review the Payments documentation for an overview of supported API routes, fee configurations, and multi-project payout settings.

Frequently asked questions

Do I need a registered business to take payments through thelastapi?

No. Because thelastapi acts as the merchant of record, you can start selling immediately without registering a company or passing identity verification. You only provide personal identification and bank details later when you want to withdraw money to your bank.

How does a customer charge appear on their credit card statement?

Transactions appear with the platform descriptor and your custom suffix as `VIBIZ, INC* <SUFFIX>`. You can configure a 1 to 10 character statement suffix in your project settings.

What happens if a customer disputes a transaction?

When a dispute is opened, the disputed transaction amount plus a $15 dispute fee is deducted from your project balance. If the dispute is resolved in your favor, that fee and amount are returned to your balance. Q