Platform Structure

Overview

SagaPay’s platform is built on a hierarchical structure that organizes payment operations across four distinct levels: Partners, Merchants, Stores, and Terminals. Each level serves specific functions and has unique responsibilities within the payment ecosystem.

Platform Hierarchy and General Payment Flow

┌─────────────────────────────────────────────────────────┐
│                       PARTNER                           │
│         (SagaPay / Payment Facilitator / ISV)          │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  ┌─────────────────┐  ┌─────────────────┐              │
│  │    MERCHANT     │  │    MERCHANT     │  ...         │
│  │   (Business)    │  │   (Business)    │              │
│  ├─────────────────┤  ├─────────────────┤              │
│  │                 │  │                 │              │
│  │ ┌─────┐ ┌─────┐│  │ ┌─────┐ ┌─────┐│              │
│  │ │STORE│ │STORE││  │ │STORE│ │STORE││  ...         │
│  │ └──┬──┘ └──┬──┘│  │ └──┬──┘ └──┬──┘│              │
│  │    │       │   │  │    │       │   │              │
│  │ ┌──┴──┐ ┌──┴──┐│  │ ┌──┴──┐ ┌──┴──┐│              │
│  │ │TERM.│ │TERM.││  │ │TERM.│ │TERM.││              │
│  │ └─────┘ └─────┘│  │ └─────┘ └─────┘│              │
│  └─────────────────┘  └─────────────────┘              │
│                                                         │
└─────────────────────────────────────────────────────────┘

Understanding Each Level

Partners

Partners are organizations that integrate SagaPay’s payment solutions into their business ecosystem. They represent the highest level in our platform hierarchy.

Who are Partners?

• Payment Facilitators (PayFacs)
• Platform Providers (PaaS)
• Independent Software Vendors (ISVs)
• Large Enterprises managing multiple merchants

Partner Types

What Partners Do:

• Onboard and manage multiple merchants
• Configure platform-wide payment settings
• Access consolidated reporting across merchants
• Manage merchant groups and hierarchies
• Set platform-level branding and configurations

Partner Capabilities:

• API credential management
• Multi-merchant reporting
• Platform-wide configurations
• Merchant onboarding automation
• Advanced security controls

Merchants

Merchants are the businesses that accept payments through SagaPay’s platform. They can operate independently or be part of a partner’s ecosystem.

Who are Merchants?

• Retail businesses
• E-commerce companies
• Service providers
• Food & beverage establishments
• Any business accepting payments

Merchant Types

What Merchants Do:

• Manage their payment operations
• Configure payment methods
• Handle transactions and settlements
• Manage store locations
• Monitor business performance

Merchant Features:

• Payment method configuration
• Store management
• Settlement handling
• Transaction reporting
• Branding customization

Stores

Stores represent physical or virtual locations where transactions occur. They are the operational units under merchants.

Types of Stores:

• Physical retail locations
• E-commerce websites
• Mobile points of sale
• Service locations
• Virtual terminals

Store Functions:

• Process transactions
• Manage terminals
• Handle day-to-day operations
• Track location-specific performance
• Manage staff access

Store Capabilities:

• Terminal management
• Staff access control
• Location-specific reporting
• Operational configurations
• Receipt customization

Terminals

Terminals are the endpoints where payments are actually processed. They can be physical devices or virtual interfaces.

Physical Terminals

Online Terminals

Terminal Features:

• Payment processing
• Receipt generation
• Customer interface
• Security compliance
• Payment method support

Hierarchical Relationships

Access Control

Configuration Flow

Top-down Settings:

• Partner configurations affect all lower levels
• Merchant settings apply to all their stores
• Store settings apply to their terminals

Override Capabilities:

• Lower levels can override certain inherited settings
• Specific configurations can be locked at higher levels
• Store settings apply to their terminals

Override Capabilities:

• Lower levels can override certain inherited settings
• Specific configurations can be locked at higher levels