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
- baa543aff574c243a0a432d79e5a62592d20fbe56937336309f9220e4c75c28e
- request
- b28994ce82f95f682d71345afe6ed137e21dda90b702ef9f8ad52d9cbfa6a060
- transaction
- f38d4e7488805dca18b12a2b18370b2fd2f4c191b7017204a79d67412d9867f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27786
the chainentry 27786
- sealed to the entry before
- db1aecdbf38d058d6c6639fd3cae60c80543612d781944131adca57316250bde
- this leaf
- 14aa0e276555d83cd7c11deb2c444b1babbaabc57492755d38448aaa5ac14a61
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mwiycAliX4/66ac862g918f9K1qJqKlm8u4EWSYDOyNgBwsQlCbst5wvazcPUg40LKhPTKMBRAEi7OzujTgiDA==