We are exploring digital data filtering and have configured one for web messaging where numbers are masked. Our current challenge is to determine how we can access the customer-entered numbers ( the original number which is masked ) within digital flows in order to execute specific logic

Once data masking is activated, it will entirely mask any the matching patterns on the ingress point, so the masked information cannot be used anywhere in the platform, for privacy reasons. What you are probably looking for is something like Secure Message Flows and/or Secure Forms, see this future Idea > https://genesyscloud.ideas.aha.io/ideas/SSA-I-561

We are exploring digital data filtering and have configured one for web messaging where numbers are masked. Our current challenge is to determine how we can access the customer-entered numbers ( the original number which is masked ) within digital flows in order to execute specific logic

Angelo,

We need to turn off the automatic credit card blocking now that customers can use digital masking.  

Also, secure input can be used for collecting but not displaying digits, correct?

Once data masking is activated, it will entirely mask any the matching patterns on the ingress point, so the masked information cannot be used anywhere in the platform, for privacy reasons. What you are probably looking for is something like Secure Message Flows and/or Secure Forms, see this future Idea > https://genesyscloud.ideas.aha.io/ideas/SSA-I-561

We are exploring digital data filtering and have configured one for web messaging where numbers are masked. Our current challenge is to determine how we can access the customer-entered numbers ( the original number which is masked ) within digital flows in order to execute specific logic

Currently Credit Card masking is enforced to comply with PCI: we may consider removing this, but we need that Secure Flow / Secure Form feature first. Yes the idea with Secure Input would be to not display those digits, but still allow to capture and store securely, for further data-processing.

Angelo,

We need to turn off the automatic credit card blocking now that customers can use digital masking.  

Also, secure input can be used for collecting but not displaying digits, correct?

Once data masking is activated, it will entirely mask any the matching patterns on the ingress point, so the masked information cannot be used anywhere in the platform, for privacy reasons. What you are probably looking for is something like Secure Message Flows and/or Secure Forms, see this future Idea > https://genesyscloud.ideas.aha.io/ideas/SSA-I-561

We are exploring digital data filtering and have configured one for web messaging where numbers are masked. Our current challenge is to determine how we can access the customer-entered numbers ( the original number which is masked ) within digital flows in order to execute specific logic

We are exploring digital data filtering and have configured one for web messaging where numbers are masked. Our current challenge is to determine how we can access the customer-entered numbers ( the original number which is masked ) within digital flows in order to execute specific logic