NPHIES

Separate sandbox testing from production authorization

Check package, certification, certificate and routing evidence before live exchange.

Current source · source reviewed · 7 min read

Before you begin

Environment-specific NPHIES configuration.
Authorized onboarding artifacts and secret-manager access for the deployment owner.

1. Identify the environment

Confirm endpoint and NPHIES configuration both refer to the intended environment. Do not connect a test package or sandbox credential to a production route.

2. Pin the authorized package

Record the onboarding-issued package and exact profile/terminology versions. The public development guide is treated as reference material and cannot close the production payload gate.

3. Validate certificate state

Review certificate identity, expiry, certification status and supported capabilities. Keep secret material in the configured secret manager; the UI and exports must not expose it.

4. Test and inspect activation states

Use test_connection and activation_states to inspect environment, package and certificate checks. A connection test cannot substitute for commercial authority or certification.

5. Run enterprise readiness

Require the full package readiness result, external evidence and deployment/UAT proof before enabling production insured financial operation.

What local evidence proves

A successful software test shows behavior against the tested configuration. It does not certify the facility, payer, taxpayer or integration. The current code intentionally blocks live submission under a public-only pin.

Rotation

Use the authorized rotate_certificate workflow to update references and certificate metadata. Verify the replacement without placing private keys or credentials into screenshots.

Troubleshooting

Connection works but live submission is refused

Read the package pin, certification, certificate-expiry, environment and authority blockers. Obtain the actual onboarding evidence instead of suppressing the guard.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.