Requesting a Stop Payment on a check disbursement

Stop payments can be requested for a variety of reasons, such as the payee not receiving the check or the disbursement no longer being needed. 

In all situations, in order for our team to process the stop payment, the check will need to have not been cashed. If the check disbursement status on the platform shows “Cleared”, our team will not be able to process a stop payment.

While the process of requesting a stop payment is the same for both Standalone Accounts and Pooled Sub-Accounts, there are differences in how funds are returned to the account. Below you will find the steps needed to make this request for both Standalone Accounts and Pooled Sub-Account trust beneficiaries, as well as timelines you can expect to have funds returned.

Standalone Accounts

To request a stop payment for a Standalone Account account, please email our team at trustsupport@truelinkfinancial.com

In your message, please include:

  • The beneficiary’s name
  • The check number

Since the funds are not debited from the account until the check is cleared, no funds will be returned.

Pooled Sub-Accounts

To request a stop payment for a beneficiary included in a pooled trust, please email our team at trustsupport@truelinkfinancial.com

In your message, please include:

  • The beneficiary’s name
  • The check number

As our team will need to place funds back in the beneficiary’s sub-account after the check has been stopped, please allow 2-3 business days for the funds to become available. Once funds are available, you will see a deposit record created by our team that confirms the request has been completed.

In both scenarios, a member of our team will follow up with you shortly after submitting your request to confirm that we were able to process the stop payment. If we have any additional questions, we’ll be sure to let you know right away.

Did this answer your question? Thank you for your feedback. If you'd like to share more, please email us at support@truelinkfinancial.com. There was a problem submitting your feedback. Please try again later.