Concept: Session-Based Payment

Goal

Enable users to access paid digital content across multiple partner websites through short-term “usage sessions”, allowing small, frictionless commitments that are settled later in a single transaction.

Actors

Role	Description
User	A person who starts a session via first commitment.
Operator	Implementator— manages sessions, settlements, and payments.
Partner	A website or publisher offering paid digital content.
Bank	Any bank used by the user to complete the settlement payment.

Key Terms

Term	Definition
Session	A temporary window (e.g., a few days) during which a user can make multiple commitments.
Commitment	A declaration by the user to pay for access to specific partner content during a session.
Settle	The process triggered by the Operator to aggregate all commitments from a session.
Report	A detailed summary of all user commitments within a session.
Payment	The user’s transfer (via bank) to the Operator after settlement.
Payout	Funds transferred by the Operator to partners after receiving user payment.

Diagram

sequenceDiagram
    title Session-Based Payment Flow

    participant U as User (Phone)
    participant O as Operator
    participant P as Seller
    participant B as Bank

    %% Start Session
    U->>O: Start session - first commitment
    O->>O: Create session ID & store metadata
    O-->>U: Session started confirmation

    %% Commitments during session
    U->>P: Access paid content
    P->>O: Verify session & log commitment
    O-->>P: Confirmation (access granted)
    note over U,P: User can repeat this step with multiple places

    %% Session ends
    U->>O: Session ends (time/limit reached)
    O->>O: Aggregate commitments (settle)
    O->>U: Send report & payment request

    %% Settlement & Payment
    U->>B: Send payment (bank transfer)
    B-->>O: Confirm funds received
    O->>P: Distribute payouts by aggregates (daily)
    O->>U: Send confirmation

We implement this standard in Poland as GetViaMsg service.