Accounts

The Account resource represents a business or individual that your platform manages.

It is the central object in the Paypercut Connect integration and acts as the primary boundary for onboarding, verification, and payouts.

Account model

Each connected account represents a legal entity that can:

Accept payments
Receive payouts
Be verified and regulated independently

All onboarding and operational data is scoped to the account.

Platform-managed accounts

Paypercut supports a platform-managed model where your platform fully controls the lifecycle of connected accounts.

In this model:

Your platform creates the account
Your platform collects and submits all required data
Your platform manages onboarding and verification flows
Your platform configures payout destinations
Your platform provides user-facing experiences

This model provides full control over the user experience but requires your platform to implement onboarding, data collection, and compliance handling.

Responsibilities

When using platform-managed accounts, your platform is responsible for:

Collecting business and identity information
Creating and updating accounts via API
Managing persons associated with the account
Uploading and attaching verification documents
Handling verification requirements and re-collection flows
Configuring external payout accounts
Monitoring account state via webhooks

Account structure

An account aggregates multiple related resources:

Core data (business profile, company, individual)
Persons (representatives, owners)
Documents (via Files API)
External accounts (payout destinations)
Capabilities (permissions to operate)
Requirements (verification state)

Most onboarding operations are performed by updating the account or its related sub-resources.

Relationship to onboarding

Accounts are the anchor of the onboarding process.

The onboarding flow consists of:

Create account

Initialize the connected account and request capabilities.

Collect required data

Use the requirements field to determine what information must be collected.

Submit updates

Update the account and related resources (persons, documents).

Verify information

Submitted data is reviewed and verified.

Enable capabilities

Once requirements are satisfied, the account becomes operational.

Account types

Paypercut accounts are designed to be fully managed by the platform.

Unlike hosted onboarding models, platform-managed accounts:

Do not rely on external dashboards for onboarding
Require the platform to implement all data collection flows
Provide maximum flexibility for user experience and business logic

This approach is suitable for:

SaaS platforms onboarding businesses
Marketplaces onboarding sellers or service providers
Platforms requiring full control over onboarding and compliance flows

When to use platform-managed accounts

Use this model if your platform needs:

Full control over onboarding UX
Custom business logic during onboarding
Integration of onboarding into your product experience
Centralized management of account data and payouts

Operational signals

To determine whether an account is ready to operate, monitor:

requirements — what is missing or pending
capabilities — what the account is allowed to do
charges_enabled — whether payments can be accepted
payouts_enabled — whether funds can be paid out

These fields should drive your platform logic.

Sections

Document uploads

Account lifecycle