# Sensitive Data - Bank Details

**URL:** <https://community.hubspot.com/t/sensitive-data-bank-details/107073>\
**Category:** Tips, Tricks & Best Practices\
**Tags:** payments-links\
**Created:** [May 14, 2024, 6:27am UTC](https://community.hubspot.com/t/sensitive-data-bank-details/107073 "2024-05-14T06:27:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aparley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/aparley/32/8573_2.png) [@aparley](https://community.hubspot.com/u/aparley)\
**Post date:** [May 14, 2024, 6:27am UTC](https://community.hubspot.com/t/sensitive-data-bank-details/107073/1 "2024-05-14T06:27:28Z")

</div>

Hello HubSpotters

I’m deligted that the senstive data public beta is live, but I’m aware you can only store the last 4 digits of a bank account number in the CRM.

However, what solutions are there for storing contact bank details.

I’ve seen a couple of integrations (albeit with only 40+ installs).

Does anyone have any best practice, workarounds, integrations, or tips on how we can hold bank details on another system but still have them associated with the contact. Obviously the solution would have to be HIPAA compliant.

Please let me know how you’ve managed to solve this.

Thank you as always community for your collective brains…

Alan

---

<div class="post-metadata">

**Author:** ![PamCotton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pamcotton/32/47916_2.png) [@PamCotton](https://community.hubspot.com/u/PamCotton)\
**Post date:** [May 14, 2024, 8:27pm UTC](https://community.hubspot.com/t/sensitive-data-bank-details/107073/2 "2024-05-14T20:27:46Z")

</div>

Hey @aparley, thank you for posting in our Community!

I would recommend to also consider implementing tokenization, where sensitive data is replaced with unique identifiers (tokens) that are meaningless to unauthorized users. This adds an extra layer of security by reducing the risk associated with storing sensitive information directly.

Lastly, don’t forget about educating your team on data handling best practices and ensuring they understand the importance of safeguarding sensitive information.

Remember, every organization’s needs and compliance requirements are unique, so it’s essential to thoroughly evaluate potential solutions and consult with legal and compliance experts to ensure your chosen approach meets all necessary standards.

To our top experts, **@crispyGTM** and **@danmoyle** any recommendations for **@aparley** matter?

Thank you,

Pam

---

<div class="post-metadata">

**Author:** ![aparley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/aparley/32/8573_2.png) [@aparley](https://community.hubspot.com/u/aparley)\
**Post date:** [May 15, 2024, 7:48am UTC](https://community.hubspot.com/t/sensitive-data-bank-details/107073/3 "2024-05-15T07:48:09Z")

</div>

Thank you Pam

---

<div class="post-metadata">

**Author:** ![danmoyle](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmoyle/32/91166_2.png) [@danmoyle](https://community.hubspot.com/u/danmoyle)\
**Post date:** [May 20, 2024, 12:17pm UTC](https://community.hubspot.com/t/sensitive-data-bank-details/107073/4 "2024-05-20T12:17:33Z")

</div>

@PamCotton nothing more to add on your suggestion for @aparley. Since it has to be HIPAA compliant, I’m hesitant until HubSpot does meet that legal requirement, honestly.