Skip to main content
Rinne uses a hierarchical company structure that enables B2B2B marketplace functionality. This model allows organizations to manage multiple merchants with complete data isolation and custom configurations.

Company types

Organizations

Organizations are parent companies that manage multiple merchants. They have the ability to:
  • Create and manage merchants
  • View aggregated data across all merchants
  • Configure pricing policies for merchants
  • Access consolidated transaction reports
  • Manage users and permissions across the hierarchy
Organizations are created by Rinne administrators and receive an API key for authentication.

Merchants

Merchants are child companies that belong to an organization. They can:
  • Process payment transactions
  • Manage external bank accounts and PIX destinations for cashouts (Cashouts)
  • Register affiliation PIX keys for receiving payments (PIX Payments)
  • Access their own transaction history
  • Configure transfer settings
Merchants are created by organizations through the API and automatically inherit the organization’s pricing policies.

Company hierarchy

The following diagram illustrates the B2B2B hierarchical structure: Each merchant operates independently with:
  • Unique API key
  • Isolated transaction data
  • Separate bank accounts
  • Individual provider affiliations
  • Custom transfer configurations

Key differences

Authentication scope

When you authenticate with an API key, the scope depends on the company type: Organization API key: Access to all merchants and aggregated data
Merchant API key: Access only to own data

Creating merchants

Organizations create merchants using the /v1/merchants endpoint:
The merchant is automatically linked to your organization and inherits your pricing policies.

Document requirements

  • Document must be exactly 14 digits
  • Tax type must be one of: PJ, MEI, or ME
  • Contact document (CPF) can be different from company document
  • declared_revenue is required

CPF companies (individuals)

  • Document must be exactly 11 digits
  • Tax type must be PF
  • Contact document must match company document

Updating document_tax_type

The document_tax_type field can be updated after company creation, but only when the company has no affiliations in non-final statuses. This means:
  • Allowed: Company has no affiliations, or only FAILED/REJECTED affiliations
  • Blocked: Company has affiliations in PENDING, IN_PROGRESS, ACTIVE, or other non-final statuses
When updating, the same document type compatibility rules apply:
  • CPF companies can only have PF tax type
  • CNPJ companies can have PJ, MEI, or ME tax type
If you need to change the tax type for a company with active affiliations, you must wait for those affiliations to reach a final status (FAILED or REJECTED) or create a new company.

Financial information

Financial information fields are required for provider affiliation and regulatory compliance. All monetary values are stored as whole reais (BRL), not cents.

Contact financial fields

Company financial fields

Celcoin provider translation

When affiliating a merchant with the Celcoin provider, financial values are translated into income/revenue tiers. Understanding these ranges helps you provide accurate financial information.
Monthly income values are mapped to the following tiers:
Total net worth values are mapped to the following tiers:
Annual revenue values are mapped to Brazilian company size classifications:

Occupation values

The following occupation values are supported: ADMINISTRATOR_MANAGER, SALES_REPRESENTATIVE, HR_ANALYST, FINANCIAL_ANALYST, SOFTWARE_DEVELOPER, MARKETING_PROFESSIONAL, HEALTHCARE_PROFESSIONAL, TEACHER, ENGINEER, LAWYER, GENERAL_SERVICES, CONSTRUCTION_WORKER, DRIVER, RECEPTIONIST, TECHNICIAN, DESIGNER, MACHINE_OPERATOR, CONSULTANT, BEAUTY_PROFESSIONAL, SECURITY_AGENT, AGRICULTURAL_WORKER, TRAVEL_AGENT, JOURNALIST, PSYCHOLOGIST, PUBLIC_SERVANT, RESEARCHER, ARTISAN, RETIRED, STUDENT, SELF_EMPLOYED, OTHER

Next steps

Affiliations

Connect merchants to payment providers

Transactions

Learn about payment processing