Payment Hub
Overview
Payment Hub provides centralized transaction management at the client level, enabling automatic or manual distribution of funds across a client's active loans. Instead of recording payments directly on individual loans, funds are received as transactions linked to the client and then allocated to credit obligations.
Why Client-Level Transactions
Traditional loan-level payment recording requires separate entries for each loan when a client makes a consolidated payment. Payment Hub addresses this by:
Single entry point — One transaction captures the total received amount
Flexible distribution — Funds can be automatically or manually allocated across multiple loans
Unified tracking — Complete payment history accessible from client record
Key Capabilities
Transaction Management
A transaction represents funds received from a client. Each transaction includes:
Client association (single client per transaction)
Payment purpose (determines distribution logic if multiple purposes configured)
Currency and amount
Document reference
Transaction date
Distribution status
Smart Distribution
Automatic allocation distributes transaction funds across client's loans based on:
Loan prioritization rules — Which loans receive funds first
Tranche ordering — Priority within credit lines
Obligation hierarchy — Order of principal, interest, fees, penalties
Distribution algorithms are configured at SDK level per project.
Manual Distribution
Users can manually create payments on specific loans from an unallocated or partially allocated transaction. The system then distributes each payment across that loan's obligations according to configured rules.
Payment Rollback
Individual payments can be canceled, returning funds to the transaction's unallocated amount. This enables:
Correction of distribution errors
Redistribution when loan conditions change
Partial or full reallocation
Transaction Lifecycle
Unallocated
Linked to client, no distribution performed
Partly Allocated
Some funds distributed, remainder available
Allocated
Fully distributed across loans
Void
Transaction canceled (only from Unallocated status)
Typical Use Cases
Multi-Loan Clients
When a client has multiple active loans:
Single transaction captures the payment
Smart Distribution allocates according to business rules
Each loan receives appropriate portion automatically
Directed Payments
When a client specifies payment should apply to particular loan(s):
Create transaction without Smart Distribution
Manually allocate to specified loans only
Remaining amount stays available for future use
Payment Corrections
When distribution needs adjustment:
Cancel incorrect payments
Funds return to unallocated
Redistribute manually or via Smart Distribution
Consolidated Payments
When receiving bulk payments (e.g., salary deductions, standing orders):
Create transaction per payment received
Automatic distribution handles allocation
Clear audit trail per transaction
Business Benefits
Efficiency
Single entry for multi-loan payments
Flexibility
Automatic or manual distribution options
Control
Payment purpose and type support complex rules
Accuracy
System-enforced validation prevents over-allocation
Audit Trail
Complete history of distributions and adjustments
Where to Configure
Distribution Rules (SDK)
Loan prioritization, obligation ordering, and distribution algorithms are defined at SDK level during implementation.
See Payment Hub — Automatic Payment Allocation in SDK documentation.
User Permissions (Admin Panel)
Transaction creation and payment management permissions are configured through Admin Panel role settings.
Related Topics
Transactions (Payment Hub) — Step-by-step transaction and payment procedures
Lending Process — Overall origination and servicing flows
Last updated
Was this helpful?