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
- 96c2bdf33b380c24718ff1cf45adc6149698c28cbdccef06facd543c20f76924
- request
- e5c7ea6751ac035e0706fbd02eedb31ea024ce16a9b1d81896420ea05b901fbd
- transaction
- 8015fbf9c0fdc096f2b17228fadae06898564ecc5b2f3fa46cfb8029feac1ca8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43629
the chainentry 43629
- sealed to the entry before
- 96d84e3d2c05d791ebd797e047db17fc1671b491ee3cfa0846ec9bea68339b84
- this leaf
- 36cbeb0aef4810121471b7ce76edbcb0b0e65078fd09cf1177214dccf626dc7c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t02qVMK3QHWTp/2D8AqiLCZiqEy+VonQN0QRhg/Tc1O/LClyTkCo6Xio4umvDWevVuXDECIcjbr/NFEt/ax9DA==