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
- 3370b8a20fc1ee0b4c363a272ffc29c3416138429f7d2e2f1093d0a73009d18f
- request
- dd18b78c80eb0cb8a78e66a579e936f8ba543d7bf7a1f751c584b106489d8dea
- transaction
- ab5965f92770e62cfcb73ce0396293f972d5cb44eed20069ec87cca6d5ca8b69computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17986
the chainentry 17986
- sealed to the entry before
- a7f17b9ccadc8ad7bf55732c7e5851c86f6133b2c5ba6af9d463b4e5393f6fcf
- this leaf
- 5a97417ef10df8fb90f6d0fb75c87fe6efb157df48d3593e40b0319b4827dd0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QiDK+/57TVHzzinO9OSp22gomRoVO7FqE+F3n94yc69TdA4CJCioI65zyvX6H9tMc9E7z70DJkqMVVjRqzRGBQ==