Overview
To ensure your Salesforce payment records accurately reflect real-world funding, our application runs two scheduled batch jobs: the Payment Deposit Batch and the Payment Status Batch. The Payment Deposit Batch pulls deposit records from the processor and stores them in the Deposit object, while the Payment Status Batch updates the transaction status accordingly (e.g., from Pending Settlement to Settled Successfully). Both batches rely on the CardConnect Funding API to keep this data synchronized.
We have recently improved this batch process for CardConnect users to provide more reliable transaction status updates and eliminate manual syncing workarounds.
Previously, our system relied on a strict date-matching system (e.g., pulling deposits from exactly 3 days ago). If CardConnect experienced a delay and the funding record was not created before our batch process ran, the system would miss that deposit entirely. Because the batch strictly looked at a single day, it would never look back to catch the missed deposit, leaving the associated payment permanently stuck in a "Pending Settlement" status in your org.
Solution
To resolve this timing issue, we have updated the CardConnect batch process to retrieve deposits using a rolling date range rather than a strict daily offset.
How it works: The system now looks back over the last several days (e.g., the last 5 days) during every batch run.
The benefit: If a deposit is delayed by the processor and posts outside of your original processing window, it will no longer be skipped. The rolling look-back window ensures that delayed funding records are automatically captured and updated correctly on subsequent batch runs.
Troubleshooting
Because the system now actively looks back over a rolling window, manual workarounds for delayed CardConnect settlements are largely a thing of the past.
If you notice a transaction stuck in "Pending Settlement," you generally do not need to take action. Once CardConnect finalizes the funding data, the next batch run will automatically detect the delayed record and sync the "Settled" status to your org.
Note: Please ensure your Payment Deposit Batch is actively scheduled and running successfully in your environment for these automated updates to occur.
Availability: Spring '26