Organizations overview

An organization is Payabli’s primary container for your business within the platform: it represents your business structure. Paypoints represent individual merchant accounts. Every paypoint belongs to an organization, and the organization determines what users can see, how settings apply, and which processors are available.

Hierarchy and paypoints

Payabli supports a single organization or a nested hierarchy of sub-organizations, depending on how you structure your business. Your instance of Payabli is an individual organization. Regional divisions, separate product lines, or distinct merchant portfolios can each become a sub-organization.

Paypoints always belong to an organization. An organization can contain many paypoints, but a paypoint belongs to exactly one organization at a time.

If you have no sub-organizations in your portfolio, your paypoints have your partner organization as their parent.

Access scoping

A user assigned at the organization level can view and act on all paypoints within that organization. A user assigned only at the paypoint level can only access that paypoint.

In a nested hierarchy, access cascades downward. A user assigned at the partner organization level can view and act on all sub-organizations and every paypoint beneath them. A user assigned at a sub-organization level can access that sub-organization, any sub-organizations nested under it, and their paypoints. They can’t access sibling sub-organizations or anything above their level.

A user’s effective role and permissions can differ depending on whether they’re operating at the organization level or within a specific paypoint. This lets you grant someone broad access across an entire portfolio or scope it to a single merchant.

Configuration inheritance

General settings — including billing, risk, and funding configuration — cascade from organizations down through any sub-organizations to paypoints. Each level inherits from the one above it unless an override is in place.

This relationship forms when you create a paypoint, so the organization you assign it to has lasting implications for its default behavior and service availability.

What you can and can’t change

You can update organization attributes like name, settings, and branding after creation. The parent-child relationship between organizations isn’t something you can change through the portal or API — contact Payabli support if you need to restructure the hierarchy.

You can move paypoints between organizations, but this isn’t a self-service action in the portal. Moving a paypoint has configuration implications. If the paypoint was inheriting settings from its original organization and the target has different settings, the paypoint may receive a new configuration profile to preserve its effective settings.

Partners with the organization_update permission can move paypoints using the migrate paypoint API. Otherwise, contact Payabli support to request a move.

You can delete an organization using the delete organization endpoint, but the organization must have no paypoints or child organizations first. This isn’t available in the portal.

Related resources

See these related resources to help you get the most out of Payabli.