Skip to content

Problem with ABA_ROUTING_NUMBER detection #94

@hmuhammad1

Description

@hmuhammad1

ABA_ROUTING_NUMBER

ID:1:Original : The transaction did not complete because the wrong routing number, XXXXXXXXX, was used instead of the correct number, XXXXXXXXX
Entity: AU_ACN, Start: 67, End: 76, Score: 1.0
Entity: ABA_ROUTING_NUMBER, Start: 67, End: 76, Score: 1.0
Entity: ABA_ROUTING_NUMBER, Start: 118, End: 127, Score: 1.0
Entity: DATE_TIME, Start: 67, End: 76, Score: 0.85
Entity: PHONE_NUMBER, Start: 67, End: 76, Score: 0.75
Entity: PHONE_NUMBER, Start: 118, End: 127, Score: 0.75
Entity: US_PASSPORT, Start: 118, End: 127, Score: 0.4
Entity: US_PASSPORT, Start: 67, End: 76, Score: 0.05
Entity: US_SSN, Start: 67, End: 76, Score: 0.05
Entity: US_BANK_NUMBER, Start: 67, End: 76, Score: 0.05
Entity: US_BANK_NUMBER, Start: 118, End: 127, Score: 0.05
Entity: US_DRIVER_LICENSE, Start: 67, End: 76, Score: 0.01
Entity: US_DRIVER_LICENSE, Start: 118, End: 127, Score: 0.01
ID:1:Anonymized: The transaction did not complete because the wrong routing number, <ABA_ROUTING_NUMBER>, was used instead of the correct number, <ABA_ROUTING_NUMBER>

Our team has been working with the ABA_ROUTING_NUBER in previous sprints. The PII Analyzer was able to generate a score that the PII was likely to be a routing number, however, the PII was identified as an AU_ACN number.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions