Platform Overview

Five endpoints. Full PayFac mechanics.
No banking license required.

PayLoop is built for vertical SaaS platforms — medical practice software, legal billing tools, dental platforms, freight TMS, salon and fitness software — that need to embed payment acceptance for their merchants without becoming a Money Transmitter or standing up a $5M compliance program. The full API surface is /onboard, /charge, /payout, /dispute, and /refund.

The Problem

Three paths for embedded payments.
All three are wrong for vertical SaaS.

When a vertical SaaS platform decides to embed payment acceptance, the standard landscape offers exactly three options — and each one has a structural problem that compounds at scale.

  • Path 1 — Refer to Stripe: You get a referral fee. Stripe owns the merchant relationship and sets pricing. You lose 30–50bps of margin that should be yours, permanently.
  • Path 2 — Build on Stripe Connect: 12–18 months of integration engineering, custom KYC/KYB flow, and you still hit Stripe's 30–40bps platform-take ceiling. Plus, Stripe Connect's compliance model leaves your platform holding several regulatory obligations it may not realize it has.
  • Path 3 — Become a PayFac: Get bank sponsorship (Synovus, Cross River, or similar), stand up your own BSA/AML program, hire a compliance team, build KYC/KYB, handle chargebacks directly. Minimum realistic budget: $5M+ and 2+ years.
PATH 4 — PayLoop API
POST /onboard
KYC/KYB via hosted form — under 10 min
APPROVED
POST /charge
Card / ACH / Apple Pay / Google Pay
SETTLED T+2
POST /payout
Platform fee deducted, remainder to merchant
50–90bps
BSA/AML: PayLoop. 1099-K: PayLoop. Disputes: PayLoop.
Smart Routing Architecture
How the API Works

End-to-end payment lifecycle
in five endpoints

PayLoop's REST API covers every step from merchant onboarding through settlement and tax reporting. Your platform calls the API; PayLoop handles the banking relationships, regulatory obligations, and money movement.

/onboard
Hosted KYC/KYB form via Persona/Alloy. Sub-merchant verified and activated in under 10 minutes.
/charge
Card (Visa/Mastercard direct), ACH via Federal Reserve, Apple Pay, Google Pay. NACHA-compliant.
/payout
T+2 standard, T+0 for vetted merchants via FedNow. Platform fee deducted at settlement.
/dispute + /refund
Built-in chargeback evidence collection. Refund flows with webhook confirmation to platform and merchant.
Subscription Revenue Dashboard
Platform Integration Points

What your engineering team
actually integrates

Webhooks for Every State Transition

PayLoop fires webhooks on charge.authorized, charge.settled, payout.initiated, payout.completed, dispute.opened, dispute.resolved, and refund.processed. Your platform's event handler drives sub-merchant notifications without polling.

Sub-Merchant + Platform Dashboards

Embedded white-label dashboard for your merchants: transaction history, settlement schedule, dispute status. Separate platform-level dashboard shows aggregate volume, per-merchant fee revenue, and 1099-K issuance status by sub-merchant.

1099-K Filing

PayLoop issues IRS Form 1099-K to qualifying sub-merchants at year end. Thresholds tracked automatically. Your platform receives confirmation of filing per merchant — zero IRS interaction required on your side.

Dispute Evidence Workflow

When a chargeback is opened, PayLoop's guided evidence collection UI prompts your sub-merchant for the specific documents the card network requires. Evidence packaged and submitted on the merchant's behalf — your engineering team does not build this flow.

PayLoop Platform Integrations

See the API against your specific vertical

A 30-minute technical walkthrough covers: your sub-merchant onboarding flow, platform fee configuration, settlement timing, and which compliance obligations shift to PayLoop vs. remain with your platform. Bring your CTO or Head of Product — this is an engineering conversation.

Book a Technical Walkthrough