Payment Connect
Payment Connect
Breadcrumbs

Release Notes

Intended Audience

These documents are intended for:

  • Salesforce Administrators

  • Finance, Accounting, and Billing Teams

  • Business Stakeholders

  • Operations Teams

  • Developers & Technical Architects

  • QA & Release Teams

  • Implementation Partners

  • Support Teams

Purpose of These Documents

The purpose of the Release Notes section is to provide a consolidated summary of new features, enhancements, bug fixes, configuration updates, and technical changes introduced in each Payment Connect product release.

These documents help teams:

  • Understand what has changed between package versions.

  • Prepare for deployments and application upgrades.

  • Review new payment functionalities and gateway integration enhancements.

  • Identify impacted billing workflows and technical dependencies.

  • Validate Custom Metadata updates or operational changes.

  • Track resolved issues and known limitations.

What These Documents Cover

The child pages under this section include release-specific documentation containing:

  • New Features & Payment Enhancements

  • Bug Fixes & Resolved Issues

  • Payment Gateway API & Integration Changes (e.g., Actum, Fiserv, UnityFi)

  • Configuration & Custom Metadata Updates

  • Apex Batch Processing & Automation Updates (e.g., Recurring Payments)

  • UI & LWC Improvements (Payment Console, Payout Console, Experience Cloud)

  • Performance Optimizations

  • Security, Tokenization & PCI Compliance Enhancements

  • Known Issues & Limitations

  • Deployment & Upgrade Notes

Typical Release Note Sections

Depending on the release scope, each release note document may include:

  • Release Version & Date

  • Executive Summary

  • Business Impact Overview

  • Feature Highlights

  • Technical Enhancements (e.g., New Invocable Methods)

  • Deprecated Features

  • Breaking Changes

  • Required Post-Deployment Steps (e.g., updating Remote Site Settings or Webhook URLs)

  • Data Migration Considerations

  • Environment-Specific Notes

  • Upgrade Recommendations

  • Rollback Considerations

  • Known Issues & Workarounds

Business & Technical Benefits

Maintaining structured release notes helps organizations:

  • Improve release transparency across IT and Finance departments.

  • Simplify upgrade planning for mission-critical payment infrastructure.

  • Reduce deployment risks and prevent revenue collection downtime.

  • Improve communication across cross-functional teams.

  • Accelerate user adoption of new payment features and self-service portals.

  • Support strict audit and governance processes.

  • Maintain historical tracking of financial system changes.

Important Note

Release Notes should be carefully reviewed before every deployment or package upgrade to understand:

  • Impacts to Custom Metadata Field Mappings.

  • Required post-installation steps (such as re-authenticating gateways).

  • Compatibility considerations with existing Salesforce Flows or Apex triggers.

  • Feature dependencies.

  • Operational or user-facing changes on the Payment Console.

Best Practice: Teams are highly encouraged to validate all new package versions and changes in a Sandbox environment using test payment gateway credentials before promoting updates to your Production org.