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
- 681b17d33625d0c6868bf9c42b7239aaedca6d821b43daee923dc15dd4a3f4e0
- request
- dbdb36e795b0c3e98a510fc1167c3144da41e5e2dd3b08739c69694aacc8aeb2
- transaction
- 5888471ae9dabdb3b03e6a53638b3f8860171b2c219e414381a111b127f83936computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16112
the chainentry 16112
- sealed to the entry before
- 37ac4fa19a45c9aaa1297169a2b0a8c9c8e167a6d550e7203ceb31e27addfb7b
- this leaf
- fa73b5c21e95645656333459ac826112f93c8f295b0b7e7e18d6996416ba0753
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 35canJvQP4esSU92tz6ecBEQsKRDztJ3K8EEOfr8WGoa1vtdlBd+D4pDQcjrnsuZvbw0xBzvk11Yo4TnpqlkCA==