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
- a6546e32b9f301f606cad75c1ebc0cedde2460d8667ff234eedb3c7f8241655c
- request
- 13445710cb6384259b59ad3902dadf62c9c14a94bed9e81b739457274d191a1b
- transaction
- 278aa7af469f550638701cccc0fce7ecf4eead873120ed48ac9f947d50f45aa9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1115
the chainentry 1115
- sealed to the entry before
- 82031f25b1550256502d17f40f56195f93980a7cceb2d534207061df48835770
- this leaf
- aaba2cb63c64c5eaac3b88b1b5c39216e9c1565ce5722e1cf1ca8bfa9837b1b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F1itC164PGmiO6QWEIVs7qcm1IpY4eKNjoIGwmjd4DPoUiEInBMDZXYn5+CyNb176kLeAcnJ42fJppexD6RABQ==