PayPlus Enterprise — Administration Guide
Document Scope
This guide covers system administration, configuration, and operations for PayPlus Enterprise v3.2. It's written for bank IT staff who install, configure, and maintain the PayPlus system. End-user operations and payment processing workflows are in the PayPlus Operator Guide.
Product Overview
PayPlus Enterprise is a multi-rail payment hub for financial institutions processing domestic and cross-border payments. It provides a unified processing engine, compliance controls, and settlement infrastructure across all major US and international payment rails — ACH, Fedwire, SWIFT, RTP, and FedNow.
PayPlus Enterprise replaces siloed, rail-specific processing systems with a single, integrated platform. All payment types share a common rules engine, approval workflow, audit trail, and compliance screening layer — reducing operational complexity and providing a consolidated view of payment activity across the institution.
Installation
System requirements, installation procedure, database setup, post-installation validation
User Management
User roles, permission matrix, LDAP integration, SSO (SAML 2.0), password policy
Payment Rail Connectors
Configuration for ACH, Fedwire, SWIFT, RTP, and FedNow connectors
Workflow Engine
Payment lifecycle, approval workflows, rules engine, STP configuration
Monitoring & Alerts
Dashboard, real-time queue, alert rules, SLA monitoring, settlement reports
Compliance Configuration
OFAC screening, hold queue management, AML integration, Travel Rule, audit trail
System Architecture
PayPlus Enterprise is a three-tier Java EE application deployed on a supported application server. The platform follows a service-oriented architecture — payment processing, compliance screening, and connector management operate as discrete services that communicate via an internal message bus.
Presentation
Web UI / API
Web UI / API
→
Application
Processing Engine
Processing Engine
→
Compliance
OFAC / AML
OFAC / AML
→
Connectors
Rail Adapters
Rail Adapters
→
Data
Oracle / SQL Server
Oracle / SQL Server
| Tier | Components | Function |
|---|---|---|
| Presentation | PayPlus Web Console, REST API Gateway | User interface for operations staff; REST API for integration with core banking and host systems |
| Application | Payment Processing Engine, Rules Engine, Workflow Manager, Audit Service | Core payment orchestration — validates, routes, approves, and submits payment instructions to the appropriate rail connector |
| Compliance | OFAC Screening Module, AML Integration Adapter, Travel Rule Engine | Mandatory compliance checks applied to every outgoing payment before submission to the rail connector |
| Connectors | ACH Connector, Fedwire Connector, SWIFT Connector, RTP Connector, FedNow Connector | Rail-specific adapters that translate PayPlus internal format to the required network message standard and manage connectivity to each payment network |
| Data | PayPlus Database (Oracle 19c / SQL Server 2019), Message Store, Audit Repository | Persistent storage for payment records, configuration, audit logs, and message archives |
Deployment Models
| Model | Description | Typical Use Case |
|---|---|---|
| On-Premises | PayPlus installed on institution-managed servers in a private data center. Full control over infrastructure, data residency, and network connectivity to payment networks. | Large banks with existing data center infrastructure and strict data residency requirements |
| Private Cloud | PayPlus deployed on institution-managed private cloud (VMware, OpenStack). Virtualized infrastructure with the operational control model of on-premises. | Institutions migrating from on-premises to cloud-managed infrastructure while maintaining control |
| Hybrid | Application and compliance tiers in private cloud; payment network connectivity (FedLine, SWIFTNet) maintained through dedicated on-premises hardware or managed connectivity service. | Institutions with regulatory constraints on cloud connectivity to payment networks |
FedLine and SWIFTNet Connectivity
FedLine Advantage (for Fedwire and FedNow) and SWIFTNet Alliance Access (for SWIFT messaging) require dedicated, certified hardware devices and cannot be deployed in public cloud environments. Plan your network topology around the physical location of these connectivity appliances before selecting a deployment model.
Supported Payment Rails
| Rail | Network | Message Standard | Connector Status |
|---|---|---|---|
| ACH | NACHA / Federal Reserve ACH, EPN | NACHA 94-character fixed-width | Available |
| Fedwire Funds | Federal Reserve Banks | ISO 20022 pacs.008 / pacs.009 | Available |
| SWIFT | SWIFTNet | MT (legacy) + ISO 20022 MX | Available |
| RTP | The Clearing House | ISO 20022 pacs.008 | Available |
| FedNow | Federal Reserve Banks | ISO 20022 pacs.008 | Available |
| Fedwire Securities | Federal Reserve Banks | ISO 20022 | Roadmap v3.5 |
Document Map
| Section | Covers | Audience |
|---|---|---|
| Installation | System requirements, installation procedure, database configuration, post-installation validation, upgrade guidance | System Administrator, DBA |
| User Management | User roles, permissions matrix, creating users, LDAP/AD integration, SSO (SAML 2.0), password policy, session management | System Administrator, Security Team |
| Payment Rail Connectors | Configuration parameters for each payment rail connector; connectivity testing; failover settings | System Administrator, Payments Operations |
| Workflow Engine | Payment lifecycle states, approval workflow configuration, rules engine, payment templates, bulk processing | System Administrator, Payments Manager |
| Monitoring & Alerts | Operational dashboard, real-time payment queue, alert rules, SLA monitoring, audit log viewer, settlement reports | System Administrator, Operations Manager |
| Compliance Configuration | OFAC screening engine, sanctions list management, hold queue, AML integration, Travel Rule, regulatory reporting | System Administrator, Compliance Officer |
| Troubleshooting | System error codes, rail-specific error codes, common issues and resolution, log file locations, support escalation | System Administrator, Support |