Payment Rail Connectors

Applies to: PayPlus Enterprise v3.2 Last updated: March 2026

Overview

Each payment rail is managed by a dedicated connector module that handles network connectivity, message format translation, and session management for that rail. Connectors are configured independently and can be enabled or disabled without affecting other rails.

Navigate to Administration > Connectors to access connector configuration. Each connector has three tabs: Connection Settings, Processing Settings, and Status & Logs.

Save Before Enabling Always save connector configuration changes before enabling the connector. Enabling a connector before saving will use the previously saved configuration, which may cause connectivity failures or incorrect processing parameters.

ACH Connector

The ACH Connector handles NACHA-formatted ACH file submission and return file processing via the Federal Reserve's FedACH system or the Electronic Payments Network (EPN). The connector manages file creation, transmission scheduling, and inbound return and NOC file processing.

Connection Settings

ParameterDescriptionExample
ach.odfi.routing.numberYour institution's ODFI routing transit number. Used as the originating ABA in the NACHA file header.021000021
ach.odfi.nameODFI name as it appears in NACHA file records. Maximum 23 characters.FIRST NATIONAL BANK
ach.networkTarget ACH operator network: FEDACH or EPN.FEDACH
ach.transport.typeFile transport protocol: SFTP or FedLine. FedLine is preferred for production; SFTP for test environments.FedLine
ach.sftp.hostSFTP server hostname (used if transport.type = SFTP).ach-prod.fedreserve.gov
ach.sftp.portSFTP port. Default: 22.22
ach.sftp.userSFTP username for authentication.fnb-ach-user
ach.sftp.key.pathPath to the SSH private key file for SFTP authentication. Key must be in OpenSSH or PEM format./opt/payplus/config/keys/ach-sftp.key
ach.outbound.directoryLocal directory where PayPlus writes ACH output files before transmission./opt/payplus/ach/outbound/
ach.inbound.directoryLocal directory where inbound return and NOC files are received./opt/payplus/ach/inbound/

Processing Settings

ParameterDescriptionDefault
ach.processing.windowsEnabled processing windows: STANDARD, SDA1, SDA2, SDA3. Separate multiple values with comma.STANDARD,SDA1,SDA2,SDA3
ach.sda.cutoff.window1Cut-off time for Same-Day ACH Window 1 submission (local time). FedACH window 1 cut-off is 10:30 AM ET.10:15
ach.sda.cutoff.window2Cut-off time for Same-Day ACH Window 2 (local time). FedACH cut-off is 2:45 PM ET.14:30
ach.sda.cutoff.window3Cut-off time for Same-Day ACH Window 3 (local time). FedACH cut-off is 4:45 PM ET.16:30
ach.file.blocking.factorNumber of records in each NACHA file block. Per NACHA specification: must be 10.10
ach.return.processing.autoIf true, PayPlus automatically posts returned items to the originating account. If false, returns require manual operations review.false
ach.noc.auto.updateIf true, Notifications of Change (NOC/COR) automatically update the stored beneficiary account details. Requires compliance review if enabled.false

Fedwire Connector

The Fedwire Connector submits and receives ISO 20022 pacs.008 / pacs.009 messages via the FedLine Advantage connection. Following the Federal Reserve's ISO 20022 migration (March 10, 2025), all Fedwire messages use ISO 20022 format. Legacy Fedwire format is no longer supported.

ISO 20022 Only — Legacy Format Retired PayPlus Enterprise v3.2 supports ISO 20022 Fedwire format only. If you are upgrading from v3.0 or earlier (which supported the legacy Fedwire format), make sure all Fedwire message templates and routing rules have been updated to ISO 20022 before enabling the Fedwire Connector in production.

Connection Settings

ParameterDescriptionExample
fedwire.abaYour institution's ABA routing number used as the originating bank identifier in Fedwire messages.021000021
fedwire.institution.nameInstitution name as registered with the Federal Reserve for Fedwire participation.FIRST NATIONAL BANK NA
fedwire.fedline.hostFedLine Advantage host address. Provided by your Federal Reserve Bank district. Not a public internet address.fedline-prod.frb.gov
fedwire.fedline.portFedLine Advantage port for Fedwire message submission.9350
fedwire.fedline.certificatePath to the FedLine digital certificate used for mutual TLS authentication. Issued by the Federal Reserve Bank./opt/payplus/config/certs/fedline.p12
fedwire.operating.startFedwire operating start time (ET). Fedwire opens at 9:00 PM ET (prior business day).21:00
fedwire.operating.endFedwire last customer transfer deadline (ET). Customer wire cut-off is 6:00 PM ET.18:00

ISO 20022 Message Configuration

ParameterDescriptionDefault
fedwire.message.type.customerMessage type for customer-to-bank credit transfers.pacs.008
fedwire.message.type.bankMessage type for bank-to-bank credit transfers (cover payments, treasury).pacs.009
fedwire.uetr.auto.generateIf true, PayPlus automatically generates a UUID-based UETR for each Fedwire payment. Required for ISO 20022 compliance.true
fedwire.lei.enabledIf true, the institution's LEI (Legal Entity Identifier) is included in outgoing Fedwire messages. Required for large financial institutions.true
fedwire.lei.valueYour institution's 20-character LEI code. Obtain from GLEIF if not yet registered.5493001KJTIIGC8Y1R12

SWIFT Connector

The SWIFT Connector sends and receives SWIFT messages via SWIFTNet Alliance Access (SAA) — the SWIFT-certified messaging interface deployed on-premises at your institution. PayPlus supports both MT (legacy) messages and ISO 20022 MX messages for the SWIFT migration period.

Connection Settings

ParameterDescriptionExample
swift.bicYour institution's 8 or 11-character BIC (Bank Identifier Code). Used as the sender BIC in all outgoing SWIFT messages.FNBKUS33XXX
swift.saa.hostHostname or IP of the SWIFTNet Alliance Access server on your internal network.saa01.bank.internal
swift.saa.portSAA MQ or WebSphere MQ listener port for PayPlus message submission.1414
swift.saa.queue.outMQ queue name for outbound SWIFT messages sent from PayPlus to SAA.PAYPLUS.TO.SAA
swift.saa.queue.inMQ queue name for inbound SWIFT messages delivered from SAA to PayPlus.SAA.TO.PAYPLUS
swift.correspondent.defaultDefault correspondent bank BIC for USD settlement if no specific routing rule applies.CHASUS33XXX

Message Type Configuration

Message TypePurposeFormat Support
MT 103 / pacs.008Customer credit transfer (single)MT + MX
MT 202 / pacs.009Financial institution credit transfer (cover)MT + MX
MT 202 COVCover payment for MT 103MT
camt.056Payment cancellation request (recall)MX only
camt.029Resolution of investigation (recall response)MX only
MT 940 / camt.053Customer statement (nostro reconciliation)MT + MX

RTP Connector

The RTP Connector connects to The Clearing House (TCH) RTP network for real-time credit transfer initiation and receipt. RTP operates 24/7/365 and uses ISO 20022 pacs.008 messages. The connector maintains a persistent connection to the TCH network.

Connection Settings

ParameterDescriptionExample
rtp.routing.numberYour institution's ABA routing number as registered with TCH for RTP participation.021000021
rtp.tch.hostTCH RTP production host address. Provided by TCH after certification. Not publicly documented.(TCH-provided)
rtp.tch.portTCH RTP production port.(TCH-provided)
rtp.tch.certificatePath to the mutual TLS certificate issued by TCH for your institution's RTP connection./opt/payplus/config/certs/tch-rtp.p12
rtp.settlement.accountYour institution's prefunded settlement account identifier at the Federal Reserve Bank of New York used for TCH RTP settlement.FRB-NY-RTP-00021
rtp.max.transaction.amountMaximum transaction amount permitted by PayPlus for RTP payments. Cannot exceed the TCH network limit of $1,000,000. Set lower for retail use cases.100000
rtp.response.timeout.secondsMaximum seconds to wait for Receiving Bank acceptance or return response before treating the payment as timed out.20
Prefunded Balance Monitoring RTP settlement requires a positive prefunded balance in the TCH joint settlement account. Configure the RTP Balance Alert (Administration > Monitoring > Alerts) to notify operations when the prefunded balance falls below a defined threshold. Insufficient balance causes RTP payment rejections.

FedNow Connector

The FedNow Connector connects to the Federal Reserve's FedNow instant payment service via the FedLine network. Like Fedwire, FedNow uses FedLine for connectivity and ISO 20022 natively. FedNow operates 24/7/365.

Connection Settings

ParameterDescriptionExample
fednow.routing.numberYour institution's ABA routing number as registered with the Federal Reserve for FedNow participation.021000021
fednow.participation.typeSEND_RECEIVE — full participation (can originate and receive). RECEIVE_ONLY — can only receive FedNow credits.SEND_RECEIVE
fednow.fedline.hostFedLine network host for FedNow. Uses the same FedLine infrastructure as Fedwire but a different service endpoint.(Federal Reserve Bank-provided)
fednow.fedline.certificateFedLine digital certificate for FedNow. May be the same certificate as Fedwire or a separate certificate depending on your FedLine provisioning./opt/payplus/config/certs/fedline-fednow.p12
fednow.max.transaction.amountPer-transaction limit. Default FedNow network cap is $500,000. Elevated limit up to $1,000,000 requires Federal Reserve approval.500000
fednow.lmt.thresholdLiquidity Management Transfer threshold. When your FedNow balance drops below this amount, PayPlus triggers an LMT from your Fed master account.10000000
fednow.lmt.transfer.amountAmount transferred from Fed master account to FedNow balance when LMT is triggered.50000000
fednow.response.timeout.secondsMaximum seconds to wait for Receiving Bank response. FedNow SLA is under 20 seconds end-to-end.15

Connectivity Testing

After configuring each connector, test connectivity before enabling payment processing:

ConnectorTest FunctionExpected Result
ACHAdministration > Connectors > ACH > Test ConnectionSFTP login succeeds; inbound/outbound directories accessible; test file transmission successful
FedwireAdministration > Connectors > Fedwire > Test ConnectionFedLine mutual TLS handshake successful; Fedwire session established; test inquiry returns valid response
SWIFTAdministration > Connectors > SWIFT > Test ConnectionMQ connection to SAA established; test message delivered to outbound queue; SAA ACK received
RTPAdministration > Connectors > RTP > Test ConnectionTLS connection to TCH test environment established; ping message returns acknowledgement within 5 seconds
FedNowAdministration > Connectors > FedNow > Test ConnectionFedLine connection established; FedNow service reachable; status inquiry returns service availability confirmation
← User Management Next: Workflow Engine →