Unlinking a True Link Visa® Prepaid Card From an Account

Unlinking a True Link Visa® Prepaid Card from an account will be necessary if you need to connect a separate card account as a disbursement option. 


For example, if your beneficiary’s family used a True Link Card issued to a family member, and now you’d like your beneficiary to use a card issued in their name, you would need to unlink the family member’s card in order to link the new one. 

Only one card can be linked to a trust account from the trust dashboard.

Our Trust Support team is able to link a 2nd card upon request. If you ever need a second card linked to a trust account, please contact our team at TrustSupport@truelinkfinancial.com

For instructions on how to connect a True Link Visa® Prepaid Card to an account, please review this article here.


How to Unlink a True Link Visa® Prepaid Card as a Disbursement Option

  1. On the “Trusts” tab of the Platform, view your beneficiary’s Dashboard.


  2. Click on the “True Link Card” tab.

    If there isn't a True Link Card tab listed, the card can be unlinked on the "Overview" tab in the "True Link Card" section of that page. The following steps will remain the same.

  3. Click on the “Account” button.
Navigating to the Account tab from a True Link Card tab
  1. Click the orange button that says, “Disconnect card from client”.
How to disconnect a True Link Card
  1. You’ll be prompted to confirm that you intend to disconnect the current True Link Visa® Prepaid Card from your beneficiary’s account. Click “Continue” to finalize the update.

  1. That’s it! The current card account will be disconnected from your beneficiary’s Dashboard, and a new card is ready to be linked if necessary.

If the disconnected card has any remaining funds that you’d like returned to the trust account, instructions on how to obtain those funds can be found in this article here.

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.