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
- 9a63b36359b8bd795d956c41e7dcb828596d63238f84de79094deaa5189a57a7
- request
- e576f0b1de7e631c1867158820d5d26e00eca6adb8abba137ef547afb10a1e33
- transaction
- 4130fad77e8822575a5bbe7cee8c05de0c0ada9d7890990092654113e89ca6b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51
the chainentry 51
- sealed to the entry before
- 311d7f2c9c82421471e8e78e0fd5554a59f0fbf5dfd79c63c863813414a793c8
- this leaf
- 30a5cc26ebe91794e682a16da5a6a55b1e0fa0d1ef4518f933ea24efa63c97ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X743R6LwneuXuKRyHouQZVbRaIton2Y0Mr3NrR64mcC8F2VRJY7DVxRPAy/ddglMiZGQxuUtjm61kuEauNlfAg==