Payment System for Processing, Reserve, and Clearinghouse Activities

For Information (RFI) – Payment System 2032L226N00005 This Notice is issued in accordance with Federal Acquisition Regulation (FAR) Part 10 for the purposes of market research and acquisition planning. It is intended to provide early notification of a potential requirement and to solicit input from industry to help shape the upcoming solicitation. This is not a Request for Proposal (RFP) or Request for Quote (RFQ), and no formal solicitation exists at this time. If and when an RFP/RFQ is released, its terms may differ from the information provided in this Notice. 1. PURPOSE. This notice seeks industry feedback to refine the scope, structure, and solicitation approach for the U.S. Department of the Treasury’s anticipated acquisition to access commercial payment platforms that offer a secure, scalable, and fully integrated digital payment platforms designed to facilitate the collection, processing, settlement, and reporting of electronic payments across multiple channels. Treasury desires access to a system that is designed to deliver high availability, strong data protection, transparent reporting, and operational efficiency while providing a user-friendly experience for both payers and administrators. Treasury anticipates a streamlined solicitation process with a short response window, projected for release in March 2026. A draft

requirements document is included with this RFI notice for additional context about what is needed, and is intended to establish a baseline. Treasury is actively seeking feedback on areas that may be overly restrictive or limit commercial innovation. The information below summarizes Treasury’s current thinking and is intended to facilitate informed and constructive industry feedback. 2. ANTICIPATED CONTRACTUAL MODEL. Any award to support this requirement will likely be procured in the following manner: Treasury is primarily interested in direct relationships with payment platform owners rather than resellers, aggregators, or other intermediaries. However, Treasury may consider responses from other organizations that can demonstrate unique value in this space. Small businesses that partner with or resell the required capabilities should clearly describe their value proposition and relationship structure with the OEM. A multiple award Indefinite Delivery, Indefinite Quantity (IDIQ) contract, or a similarly flexible contractual vehicle, directly with payment platform owners. The contract(s) will be available for use across the Treasury enterprise and by other Federal entities. The resulting award will likely include an onramp/offramp capability to ensure continued competition and access to cutting edge approaches/technologies in this space. The anticipated

period of performance is one base year with up to four option years. Evaluation of the contracts (or orders) may use streamlined or alternative approaches, such as oral presentations, demonstrations, or comparative evaluations. Treasury is particularly interested in

pricing approaches that reflect direct OEM engagement, high-volume government usage, and provides the government with the most favorable economics relative to standard commercial offerings. NOTE: There is no incumbent contractor currently supporting this effort. 3. APPLICABLE CODES NAICS: 522320 – Financial Transactions Processing, Reserve, and Clearinghouse Activities PSC: 7A21 - Business Application/Application Development Software as a Service 4.

EVALUATION CRITERIA (ANTICIPATED). Quotes or submissions for any resulting solicitation may be evaluated based on some or all of the following criteria: 4.1 Technical Capability and Platform Maturity Under such a factor, the Government may consider: Breadth and maturity of payment processing capabilities, including support for required payment methods and transaction types; Fraud prevention, risk management, and chargeback handling effectiveness; Scalability and demonstrated ability to support high transaction volumes with consistent performance; Quality and usability of reporting, reconciliation, and financial transparency features; Ease of integration and flexibility of deployment options (e.g., APIs, hosted solutions); Demonstrated experience providing similar payment processing services to organizations of comparable size and complexity. 4.2 Security and Regulatory Compliance Under such a factor, the Government may consider: PCI-DSS compliance status and overall security architecture; FedRAMP authorization status (or clear path to authorization, if applicable); Strength of encryption, access controls, monitoring, and incident response capabilities; Ability to support audit, oversight, and regulatory reporting

requirements. 4.3 Cost Efficiency and