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
- 6fa826bfd6fefeb8952369b902a159d70420c8df4bdae438bb27c3931a69048d
- request
- 2ac538810590499cc57218cf80e3406c3215b06585679560347cef960464cc9f
- transaction
- cd0eb8f7e09e57d8601efd781d050653e3c87fe91083f20f5ba3f8ae62ab1d24computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31844
the chainentry 31844
- sealed to the entry before
- c9ac4c2eab32e31eff98e6294a2c11720032202928114f311b799af452158ab2
- this leaf
- e149154046bd6a0a6b58ee7492c54ba6c4aecd788a499652a90dc02e7e563be6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MyDTJeqXIgxWB1Ke33GirQDm9xr9KSuGN9ERjZ0DFZ/9FNsSKNJedYK1J13DUl056YC2fpa44cvCFXI5COP6AQ==