why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- c7f877d14feecb1a6687576395b93c22c62cf05aafc4a8905101eef36cf18973
- request
- 11e5892cee6042188993ea773684d650c324a06137657d769872872deaf40b2a
- transaction
- 77a07572fdc1b9d392801a47201be2e666e6f96d5fadbb0967aac894c95083b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20964
the chainentry 20964
- sealed to the entry before
- 2e4446abcee31ec794cad4ebb64fd3bd8b9722576b79df7c53dfd7237a9eca5c
- this leaf
- c4309992f7deb887eb6345d449b7ea8c5036140f75e9b8d93469a56115a320a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DYnuZArcd93VrZUUy1ehdQ69WgR+ayyg56SoSvWSosI4MPFG21KMEejciQDVB9vWFkZBrjc6yVu0r7dPgMeWBQ==