payment-gateway.app Docs
Releases

Release 4.2.1

Stable release notes for Payment Gateway App 4.2.1.

Release 4.2.1

  • Channel: stable
  • Deployment target: production
  • Published: 2026-04-03T20:48:25Z
  • Release tag: v4.2.1

[4.2.1] - 2026-04-03

Customer-Facing Changes

Admin Panel

  • Improved authentication retry behavior and user feedback.
  • WebAuthn timeout handling and user-friendly error messages for registration and authentication.
  • User management features and role-based access control in member settings.
  • Session refresh error logging and date-only formatting/parsing utilities.
  • Tax rate code resolution behavior and updated rendering for tax summaries.

APIs And Integrations

  • Self-role change restrictions and enhanced organization user management features.
  • Improved JWT refresh handling and session validation checks.
  • Transaction tax snapshot normalization and improved country code validation.
  • Revenue report endpoints and payment event notifications for VAT OSS services.
  • Improved tax calculation behavior, item normalization, and item merging support.
  • Preserved computed fields in GoCardless and Stripe providers.
  • Improved notification scheduling for tax-aware payment events.
  • Improved checkout status handling and transaction filters.

Checkout And Customer Portal

  • Ability to change payment methods when multiple providers are available.

Deployment And Operations

  • Updated canonical country code and buyer country filters to allow "UNKNOWN" values.

Fixes

  • Improved formatting and readability of confirmedBy fields and tax detail descriptions.
  • Improved session refresh error handling for rate limits and non-parsable responses.

Deployment Notes

Use the updater from payment-gateway-deploy to install this release. Exact image references and digests are resolved from signed release metadata and deployment tooling instead of being duplicated in these notes.

Security Artifacts

This release was published before the current release security artifact contract was made customer-facing. Use Release Security Transparency for the current SBOM, vulnerability report, policy-result, checksum, and provenance evidence model.

On this page