payment-gateway.app Docs
Releases

Release 5.0.0

Stable release notes for Payment Gateway App 5.0.0.

Release 5.0.0

  • Channel: stable
  • Deployment target: production
  • Published: 2026-08-27T17:31:27Z
  • Release tag: v5.0.0

Admin Panel

  • Sandbox environments now strictly enforce staging boundaries to prevent accidental cross-environment data leakage or execution.
  • Reduced the administrative overhead for software license audits by minimizing the runtime dependency surface and ensuring license metadata remains discoverable.

APIs And Integrations

  • Instant Payment Notifications (IPN) now include checkout attempt identifiers to improve reconciliation between merchant systems and the gateway.
  • Enhanced payment completion logic to ensure durable persistence of transaction effects, improving reliability during high-load periods or network instability.

Deployment And Operations

  • Added support for multi-architecture deployments (including ARM64 and AMD64) with native cross-compiled binaries for the reverse proxy and backend services.
  • Transitioned backend components to hardened, static runtime base images to improve stability and reduce container footprints.
  • Integrated automated Software Bill of Materials (SBOM) generation into the build process to assist operators with asset inventory and compliance requirements.

Security

  • Achieved comprehensive supply-chain compliance through the implementation of cryptographically verified build evidence.
  • Integrated automated build-evidence verification to ensure the integrity of software artifacts throughout the delivery pipeline.
  • Improved release reliability by keeping deployed artifact version metadata consistent across environments.

Fixes

  • Resolved an issue where build evidence checks were inconsistently applied during specific deployment workflows.
  • Improved the consistency of OCI image revision metadata to ensure accurate version tracking across distributed environments.

Security Artifacts

Release security evidence is linked from the Release Security Transparency guide.

On this page