ForjioHuudisIdentityPlugipayPaymentsStorlaunchE-commerceFulkrumaFulfilmentRiplloMarketingLinkSnapShort URLsPawpadoGPU streaming
Plugipay Docs
⌘K

Introduction

Plugipay is a payment infrastructure platform that helps you accept payments online without the boilerplate. Today you run it in bring-your-own-provider mode — you plug in your Xendit, Midtrans, or PayPal account and Plugipay handles the orchestration, webhooks, refunds, and reconciliation on top. A fully managed mode — where Plugipay handles the payment provider for you — is launching soon.

This documentation covers everything: getting started, the portal, the CLI, the public API, and our SDKs for Node.js, Python, and Go.

New to Plugipay? Start with the Quickstart — you'll have a working payment flow in about five minutes.

What's here

The docs are organized into the way you'll use the product over time:

  • Getting started — sign up, install the SDK or CLI, take a payment end-to-end.
  • Core concepts — the model behind customers, checkout sessions, payments, refunds, and how money moves.
  • Authentication — how sign-in, sign-up, and password resets work. We use Huudis as the identity provider so the flow is shared with every other Forjio product.
  • Portal — per-feature tours of what you can do in the dashboard at plugipay.com.
  • CLI — the plugipay command-line tool: installation, auth, every command group, and scripting recipes.
  • API reference — the public REST API: authentication, conventions, every resource, webhooks, rate limits.
  • Providers — how each payment provider works under the hood (Plugipay managed, Xendit, Midtrans, PayPal).
  • SDKs — per-language guides for @forjio/plugipay-node, plugipay on PyPI, and github.com/hachimi-cat/saas-plugipay/sdk/go.

Two modes, one API

Plugipay has two operating modes you can pick per workspace:

  • Bring-your-own-provider — you connect your existing Xendit, Midtrans, or PayPal account. We orchestrate flows, store sessions, deliver webhooks, but the funds settle to your provider account. This is what's live today.
  • Plugipay managed — we own the payment provider relationship, so you don't need a Xendit or Midtrans account. Fastest to set up, lowest configuration.

You always use the same API regardless of mode. The provider is a workspace-level setting, not a per-call parameter.

Managed payments are launching soon — Plugipay is finalizing its platform registration with Xendit. Until then, use a BYO provider (Xendit / Midtrans / PayPal with your own keys) or manual transfer. Switching BYO → managed later will work without code changes — you'll just swap the provider config in the portal.

A note on the Forjio family

Plugipay is part of the Forjio family — a set of independent SaaS products that share identity (Huudis SSO), billing (Plugipay itself, for non-Plugipay products), and design conventions. If you've used Storlaunch, Fulkruma, Ripllo, LinkSnap, Pawpado, or Catentio, the auth and SDK shapes here will feel familiar.

Each product owns its own bounded context. Plugipay owns payments, refunds, subscriptions, and the merchant-facing payment portal. It does not own customer profiles for non-payment use cases, product catalogs, or marketing automation — those live in their respective Forjio products.

Reach us

Ready? Go to the Quickstart.

Plugipay — Payments that don't tax your success