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
- 8bcae68772f8d7d5025b72caa379200439048bd5b115aa0e9c2708be2393aa47
- request
- 6aaf691952a694aadab061cb34e52e7ef12f2dd2c690d7cf775318dd058c291a
- transaction
- 562ef49499046db41ac7e1026c8531beb12e4dbccf1ffe5001c8e2205463e7a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13668
the chainentry 13668
- sealed to the entry before
- 3a06e118b1ac1da38d2f11bf314247f1c8ca1441520cd8ae45e791b0cfcd780b
- this leaf
- b3b69022f9949ae26cf6546177b5d6e6f52a631a673403ec54b8310209b505e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p3kkkZG+J9vW0k1vvByTKArpihkO4PFArDlFfjWqX/rL/5pL8cDgp3FpW2Eqf61l+wCXK9egoMmkV4jwSHxLDg==