The purpose of this page is to provide a clear and actionable checklist of essential steps that must be completed before and after a Salesforce Sandbox Refresh for the Payment Connect application.
A sandbox refresh resets the environment to match production data but may impact critical configurations, payment gateway credentials, and metadata settings.
1. Before Refresh
During a sandbox refresh, Salesforce only includes metadata and data defined in the Sandbox Template.
Objects not explicitly included in the template will not be copied into the refreshed sandbox, which can affect gateway and configuration settings in Payment Connect.
✅ Action Required:
Make sure the following objects and metadata types are included in the Sandbox Template before initiating the refresh:
-
Payment Connect Common Setting – Common app-level settings and mappings.
-
PaymenGuru Field Mapping (optional) – Field Mapping from the source object.
-
Parent Field Mapping (optional) – To populate the source object lookup on payment transaction.
2. Gateway Credentials
After a sandbox refresh, Named Credentials, Custom Settings, Custom Metadata credentials, or sensitive gateway keys are not copied from Production for security reasons.
✅ Action Required:
-
Re-enter or validate credentials for all active gateways under gateway records.
-
Confirm the Base URL, Username, Password, and Merchant ID values for:
-
Actum
-
Fiserv
-
UnityFi
-
-
Test authentication for each gateway via the Payment Console.
Failure to update credentials will result in authentication errors and failed payment processing.
3. Verify Gateway Configuration
After restoring credentials, ensure that gateway-specific configurations are correct.
✅ Action Required:
-
Verify that enabled payment methods and frequencies (e.g., one-time, recurring) are correctly set in gateway record.
-
Ensure gateway status mappings are valid in Payment_Guru_Common_Settings__mdt.
-
Confirm that sandbox test modes are active (if applicable) to avoid live transaction attempts.
4. Test Payment Workflows
Run quick validation tests for each core Payment Connect workflow:
-
Payment Request – Send and complete a payment link
-
Payment Console – Perform a direct debit test
-
Payout Console – Validate payout authorization
Check that all test transactions appear under Payment Transaction records with correct status updates.
5. Support
If you encounter any issues with credentials, gateway validation, or metadata references after the sandbox refresh:
-
Contact the Payment Connect Admin team or
-
Contact Cloud Maven support team: support@cloudmaveninc.com.