SAIF.Business.EPay.USBank dependencies

Internal dependencies

Dependency	Reference Type	Usage
(none)	NuGet Package	The project file contains no <ProjectReference> items, so this library does not depend on sibling source projects at compile time.
SAIF.BOF.Framework	NuGet Package	(vpackages.config) Supplies BOF persistence abstractions such as clsBusinessBase, clsBusinessCollection(Of T), IBusinessCriteria, IDataPortalInfo, IDataRequest, and clsResultSet.
SAIF.BOF.Business.*	NuGet Package	(vpackages.config) Supplies broader SAIF business abstractions consumed transitively by the packaged component.
SAIF.Services.WebServices.Epay	NuGet Package	(vpackages.config) Supports US Bank admin single-sign-on payload creation used by admin redirect flows.
SAIF.Web.API.Clients	NuGet Package	(vpackages.config) Provides shared SAIF client-side integration support referenced by the package manifest.

External dependencies

Dependency	Version	Usage
BankValidator	packages.config	Packaged legacy bank-validation dependency referenced by this library's package set.
Oracle.ManagedDataAccess	packages.config	Aligns with the Oracle provider registration and Oracle SQL syntax used by BOF criteria classes.
SAIFEncrypt.dll	Local binary reference	Decrypts stored bank account and routing values immediately before outbound SOAP requests.
SAIFElevate.dll	Local binary reference	Provides proxy-account impersonation used to read the external USBank constants file from a UNC share.
Generated SOAP proxies (epayWebServiceService, wsUSBankSessionTransferServices*)	Generated contract code	Expose the primary US Bank gateway contract and the SAIF session-transfer wrapper used by handwritten integration code.

Dependency risks and notes

• Runtime configuration depends on a hardcoded external UNC path that must be reachable under the impersonated proxy identity.
• Two binary dependencies (SAIFEncrypt.dll and SAIFElevate.dll) are referenced directly instead of through NuGet packaging.
• The library relies on generated SOAP proxies for both the US Bank gateway and the session-transfer wrapper, so contract drift must be resolved through proxy regeneration rather than handwritten fixes.
• Oracle provider registration is present locally, but the library does not define its own connection string or connection-key constant.

Related documentation

• Index
• Overview
• Architecture
• Operations and processes
• Business rules
• Database tables
• Security and authorization
• SQL catalog
• API reference
• Configuration

Sources

• Business\SAIF.Business.EPay.USBank\SAIF.BOF.Business.EPay.USBank.vbproj
• Business\SAIF.Business.EPay.USBank\packages.config
• Business\SAIF.Business.EPay.USBank\app.config
• Business\SAIF.Business.EPay.USBank\USBankAPIs.vb
• Business\SAIF.Business.EPay.USBank\RemotePostFiller.vb
• Business\SAIF.Business.EPay.USBank\USBankCodes.vb
• Business\SAIF.Business.EPay.USBank\epayWebServiceService.vb
• Business\SAIF.Business.EPay.USBank\Web References\wsUSBankSessionTransferServices\Reference.vb
• Business\SAIF.Business.EPay.USBank\Web References\wsUSBankSessionTransferServices1\Reference.vb