Once you've completed your planning phase, you're ready to set up technical connectivity. The connection process varies based on your chosen access method (or the access method chosen by your vendor).
API Integration Setup
API integration provides real-time access to Do Not Pay Connect services through secure RESTful web services. Our API uses certificate-based mutual TLS (Transport Layer Security) authentication to ensure secure communication between your systems and our services.
To begin API integration, you'll need to request API credentials and generate a certificate signing request (CSR) using your organization's public key infrastructure. Our certificate management guide walks through the complete process, including certificate generation, installation, and renewal procedures. We provide Software Development Kits (SDK) with libraries for Java, .NET, Python, and Node.js that handle certificate management and API communication, allowing your developers to focus on business logic rather than security infrastructure.
The initial API connection setup typically takes 3-5 business days from credential request to test environment access. Plan for additional time if you need to work through your agency's PKI or security approval processes.
API Integration Guide (Coming soon)
Download Certificate SDKs (Coming soon)
File-Based Integration Setup
File-based integration uses secure file transfer protocol (SFTP) to exchange batch files between your systems and Do Not Pay Connect. This method supports high-volume processing and integrates seamlessly with existing payment processing workflows. Other potential file transfer methods include Connect:Direct and MoveIT Transfer.
Existing Connection Users: If your agency already maintains an SFTP connection with Fiscal Service for other systems, you can extend that connection for Do Not Pay Connect. This process involves requesting additional directory access and configuring file routing. The Do Not Pay team will coordinate with the appropriate resources to use any existing connections.
New Connection Setup: Agencies without existing Fiscal Service connections need to complete our SFTP onboarding process. This includes IP address registration, SSH key exchange, firewall rule configuration, and connectivity testing. The Do Not Pay team will coordinate with the appropriate resources to establish new connections.
Product Migration: If you're converting an existing file-based integration to Do Not Pay Connect from a legacy Do Not Pay product, use our migration guide and SDK. These tools help map your file formats to our standardized schemas and validate the conversion before production deployment.
Connection Validation
After completing your connection setup, test connectivity before proceeding to QA. Our connection diagnostic tools verify certificate installation, network routing, and authentication configuration. Successful connection validation is required before receiving QA environment access.
Need Help?
If you encounter issues during connection setup or don't receive QA access approval within five business days of your request, our integration support team is here to assist.
Integration Support: DoNotPay@fiscal.treasury.gov
Phone Support: 855-837-4391 (Monday-Friday, 7:00 AM - 8:00 PM ET)
Include your agency name, connection type (API or file), and a description of your issue when contacting support. Our typical response time is within one business day.