Overall my credit card patterns are hitting as expected. However, there are instances where we get an event triggered for credit card when someone may just be browsing an internet site like foxnews.com In researching many cases across 100's of events -- it appears the data triggering the credit card event is always proceeded by a "." (period). I have not seen where any valid events would follow this pattern -- so if there is a way to weed out any events where the number is proceeded with a "." period -- then I do not think it would impact any valid events and would reduce the chatter.
Anyone else seeing this or have a regex pattern where it takes into account a proceeding specific character?