---
title: SAIF.Business.EPay.USBank overview
summary: High-level purpose, scope, and responsibilities for the SAIF.Business.EPay.USBank library.
status: draft
owner: SAIF
last_reviewed: 2026-07-24
library: SAIF.Business.EPay.USBank
reference_type: package
---

# SAIF.Business.EPay.USBank overview

> **Documentation context:** Packaged Component (NuGet)

`SAIF.Business.EPay.USBank` is a legacy .NET Framework integration library that connects SAIF payment workflows to US Bank ePay SOAP services, stores SAIF-side user and nonpayment-notice records, prepares session-transfer form posts, and parses callback and remittance XML for downstream consumers.

## Purpose
- Bridge SAIF business data to US Bank ePay SOAP contracts for user provisioning, account maintenance, recurring ACH setup, payment-management lookups, and health checks.
- Persist SAIF-owned integration state in `US_BANK_USER` and `US_BANK_NONPAY_NOTICE` so callers can correlate bank-side activity with local policy and user identifiers.
- Assemble customer and admin session-transfer payloads for browser redirects into the US Bank payment experience.
- Convert inbound US Bank XML payloads into strongly typed adapters that downstream code can consume without re-parsing XML.

## Responsibilities
- Manage SOAP client creation, endpoint selection, and certificate attachment for the primary US Bank gateway.
- Normalize outbound names, addresses, bank-account metadata, return URLs, and admin user IDs before transmitting them to US Bank.
- Centralize EPAY, ONLINE, and external XML constants-file lookups used by the integration.
- Persist and retrieve US Bank user and nonpayment-notice business objects through BOF criteria SQL.
- Surface caller-supplied provider interfaces for policy, user, address, and page context.

## Key components
- `USBankAPIs`: Handwritten gateway façade over the generated US Bank SOAP client.
- `RemotePostFiller`: Session-transfer payload builder for customer and admin payment flows.
- `clsUSBankUser` and `clsUSBankNonpayNotice`: BOF-backed persistence models for SAIF-owned integration records.
- `USBankCodes` and `USBankConstants`: Configuration and constants readers for EPAY properties, proxy credentials, and external XML values.
- `RealTimePaymentConfirmation`, `RealTimeNonPaymentNotification`, `RemittanceDocument`, and `RemittedPayment`: XML adapters for callback and remittance payloads.

## Related documentation
- [Index](index.md)
- [Architecture](architecture.md)
- [Dependencies](dependencies.md)
- [Operations and processes](operations-processes.md)
- [Business rules](business-rules.md)
- [Database tables](database-tables.md)
- [SQL catalog](sql/index.md)
- [API reference](api/index.md)
- [Security and authorization](security-authorization.md)
- [Configuration](configuration.md)

## Sources
- `Business\SAIF.Business.EPay.USBank\SAIF.BOF.Business.EPay.USBank.vbproj`
- `Business\SAIF.Business.EPay.USBank\SAIF.BOF.Business.Epay.USBank.nuspec`
- `Business\SAIF.Business.EPay.USBank\USBankAPIs.vb`
- `Business\SAIF.Business.EPay.USBank\RemotePostFiller.vb`
- `Business\SAIF.Business.EPay.USBank\clsUSBankUser.vb`
- `Business\SAIF.Business.EPay.USBank\clsUSBankNonpayNotice.vb`
- `Business\SAIF.Business.EPay.USBank\USBankCodes.vb`
- `Business\SAIF.Business.EPay.USBank\USBankConstants.vb`
- `Business\SAIF.Business.EPay.USBank\RealTimePaymentConfirmation.vb`
- `Business\SAIF.Business.EPay.USBank\RealTimeNonPaymentNotification.vb`
- `Business\SAIF.Business.EPay.USBank\RemittanceDocument.vb`
- `Business\SAIF.Business.EPay.USBank\RemittedPayment.vb`