Integrations

Connect Paprel to the systems your books depend on

Paprel is API-first infrastructure, not a connector marketplace. Payments, banks, email, your own product, and AI agents all reach the ledger through one OpenAPI surface, signed webhooks, OAuth 2.1, and MCP. Here is what plugs into the books.

OpenAPI 3.1
159 documented endpoints
Webhooks
Signed, content-hashed, idempotent
OAuth 2.0 / 2.1
PKCE, tenant-scoped tokens
MCP
Governed agent tool access
Regions
US · EU · APAC, data-pinned
Export
CSV / JSON, no lock-in

What connects to the ledger

Integration surfaces, not lock-in

Each surface writes to or reads from the same source of truth, so what your customers see in your product always matches the books underneath.

Payments & payouts

Connect Stripe Connect, configure payment gateways and modes, and take invoice payments — every charge and payout posts to the same double-entry ledger.

  • Stripe Connect onboarding
  • Configurable payment gateways
  • Invoice payments → journals

Bank feeds & reconciliation

Bring bank activity in through the transactions API — your own aggregator or feed — then match, group, exclude, and post reconciliations against the ledger of record.

  • Transactions ingestion API
  • Match / group-match / exclude
  • Reconciliation records

Your product (events → journals)

Turn product events into balanced journals over REST, and receive signed webhooks back for posted journals, approvals, exceptions, and reconciliation.

  • Double-entry journals API
  • Signed, idempotent webhooks
  • Event-driven, real-time

AI agents (MCP)

Expose the ledger to AI agents through a Model Context Protocol surface with scoped tokens — agents inspect balances and draft activity within the permissions you grant.

  • MCP-native tool access
  • Scoped, role-aware tokens
  • Agent edits land as drafts

Multi-currency & tax

Configure per-tenant currencies and tax rules so journals, invoices, and reports stay correct across regions and entities.

  • Per-tenant currencies
  • Tax configuration API
  • Multi-entity books

Email & notifications

Send invoices and notifications from your own domain with SMTP configuration and branded email templates — part of a white-label, brand-owned experience.

  • SMTP configuration
  • Branded email templates
  • Brand-owned delivery

Data export & portability

No lock-in: every journal, audit entry, and report is exportable as CSV or JSON, in the same shape as the OpenAPI spec, so you can rebuild your books anywhere.

  • CSV / JSON export
  • Same shape as the API
  • 7-year signed audit retention

Auth & access

Standard OAuth 2.0 / 2.1 with PKCE, tenant-scoped tokens, and per-route grants — the same model powers RBAC, MCP, and machine-to-machine clients.

  • OAuth 2.0 / 2.1 + PKCE
  • Tenant-scoped tokens
  • RBAC & M2M clients

Don't see a surface you need? The full OpenAPI 3.1 reference documents every endpoint, and the general ledger API is the write surface everything else builds on.

Primary Fit

Built for platforms embedding accounting into their product

Paprel is designed for SaaS, fintech, marketplace, and accounting-led products that need ledger-backed accounting workflows inside their own product experience.

Platform Teams

Evaluate embedded accounting for your product

Explore how SaaS, fintech, and business software teams can bring accounting, reporting, and automation into their own product with Paprel.

Best for product teams, engineering leads, and platform operators

Explore Embedded Accounting

Implementation Teams

Plan a governed rollout

Review deployment models, permissions, reporting, audit history, OAuth, and MCP-ready workflows before bringing accounting into your product roadmap.

Best for product, engineering, security, and finance stakeholders evaluating platform rollout

Talk Through Rollout