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 their own bank accounts
  • Create PIX keys for receiving 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

FeatureOrganizationMerchant
Create merchants✅ Yes❌ No
Process transactions✅ Yes✅ Yes
View all merchant data✅ Yes❌ No
Set pricing policies✅ Yes❌ No
Manage affiliations✅ Yes✅ Yes

​
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 
# List all merchants
GET /v1/merchants

# View all merchant transactions
GET /v1/merchants/transactions
Merchant API key: Access only to own data 
# View own transactions
GET /v1/transactions

# Manage own affiliations
GET /v1/affiliations

​
Creating merchants

Organizations create merchants using the /v1/merchants endpoint: 
curl -X POST https://api-sandbox.rinne.com.br/core/v1/merchants \
  -H "x-api-key: YOUR_ORG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "full_name": "Store Name Ltda.",
    "document_number": "16525269000121",
    "document_type": "CNPJ",
    "document_tax_type": "PJ",
    "mcc": "5912",
    "contact": { ... },
    "address": { ... },
    "transfer_configurations": { ... }
  }'
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

​
CPF companies (individuals)

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

​
Next steps

Affiliations

Connect merchants to payment providers

Transactions

Learn about payment processing