Neural Payments | Trust Center

Neural Payments Trust Center

Welcome to the Neural Payments Trust Center. We are committed to protecting the confidentiality, integrity, and availability of our customer's data. This site details how we accomplish this, our industry compliance, and provides the ability to request our security documentation.

Resources

Our latest security and compliances resources, reports, and documentation.

SOC 2 Type 2 Report

Evidence period April 14, 2025 - April 30, 2026

SOC 2 Type 2 Bridge Letter

Quarterly SOC bridge letter dated June 22, 2026

PCI-DSS v4.0.1 SAQ-D Attestation of Compliance

Updated March 25, 2025

PCI-DSS v4.0.1 SAQ-D Attestation of Compliance Bridge Letter

Updated May 28, 2026

Standard Information Gathering (SIG) Questionnaire

Updated July 1, 2026

High Level System Diagram

Updated May 2, 2025.

Penetration Test Attestations

Penetration Tests completed January 27, 2026.

Certificate of Insurance-Directors, Fiduciary, Cyber Liability, and Theft

Certificate of Insurance-General Liability, Data Breach, and Failsafe

Privacy Policy

Monitoring

Continuously monitored by Secureframe

Change Management

Availability

Organizational Management

Confidentiality

Vulnerability Management

Incident Response

Risk Assessment

Network Security

Access Security

Physical Security

Subprocessors

The Neural Payments solution employs the services of the following subprocessors.

Aptys

FedNow Connectivity via API Integration.

Auth0

Single Sign On Authentication

FIS Global

Neural Payments utilizes the FIS-NYCE Payment Processing service.

Github

Software Development Version Control

Google Cloud

Cloud Services

PayPal

Payment Endpoint Solution

Pidgin

FedNow Connectivity via API Integration

Prizeout

Payment Endpoint Solution

SendGrid

Email API

Compliance

Neural Payments complies with the following frameworks.

SOC 2 Type 2

PCI

PCI-DSS v4.0.1

FAQs

Where can I address any additional vendor due diligence requests I may have? ddr@neuralpayments.com

Monitoring

Change Management

Secure Development Policy A Secure Development Policy defines the requirements for secure software and system development and maintenance.

Software Change Testing Software changes are tested prior to being deployed into production.

Production Data Use is Restricted Production data is not used in the development and testing environments, unless required for debugging customer issues.

Availability

Uptime and Availability Monitoring System tools monitor for uptime and availability based on predetermined criteria.

Testing the Business Continuity and Disaster Recovery Plan The Business Continuity and Disaster Recovery Plan is periodically tested via tabletop exercises or equivalents.

Backup Restoration Testing Backed-up data is restored to a non-production environment at least annually to validate the integrity of backups.

Organizational Management

Internal Control Policy An Internal Control Policy identifies how a system of controls should be maintained to safeguard assets, promote operational efficiency, and encourage adherence to prescribed managerial policies.

Personnel Acknowledge Security Policies Internal personnel review and accept applicable information security policies at least annually.

Roles and Responsibilities Information security roles and responsibilities are outlined for personnel responsible for the security, availability, and confidentiality of the system.

Confidentiality

Disposal of Customer Data Upon customer request, Company requires that data that is no longer needed from databases and other file stores is removed in accordance with agreed-upon customer requirements.

Retention of Customer Data Procedures are in place to retain customer data based on agreed-upon customer requirements or in line with information security policies.

Data Classification Policy A Data Classification Policy details the security and handling protocols for sensitive data.

Vulnerability Management

Vulnerability and Patch Management Policy A Vulnerability Management and Patch Management Policy outlines the processes to efficiently respond to identified vulnerabilities.

Incident Response

Incident Response Plan Testing The Incident Response Plan is periodically tested via tabletop exercises or equivalents.

Incident Response Plan An Incident Response Plan outlines the process of identifying, prioritizing, communicating, assigning and tracking confirmed incidents through to resolution.

Risk Assessment

Risk Assessment Formal risk assessments are performed, including the identification of relevant internal and external threats related to security, availability, confidentiality, and fraud, and an analysis of risks associated with those threats.

Network Security

Endpoint Security Company endpoints are managed and configured with a strong password policy, anti-virus, and hard drive encryption.

Access Security

Complex Passwords Personnel are required to use strong, complex passwords and a second form of authentication to access sensitive systems, networks, and information.

Physical Security

Physical Security Policy A Physical Security Policy that details physical security requirements for the company facilities is in place.

Communications

Communication of Security Commitments Security commitments and expectations are communicated to both internal personnel and external users via the company's website.

Privacy Policy A Privacy Policy to both external users and internal personnel detailing the company's privacy commitments.