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
- 79783935c27ba00efd7d2ab562aaf2897cc671ab54891e8c18b611062ba33fcd
- request
- f174af80b681ab1373942ef452d00263acca1458861cba59a4e92ca9d94776ee
- transaction
- 4f1b133a059622d62a19c212675b163c0bd79862aa30988d7b977725b39f12b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8073
the chainentry 8073
- sealed to the entry before
- 5f274a5f7fe323c98d7951d7a887ea2496ad31ef85aec896f43a30a016f06bc0
- this leaf
- 0e6edd7c8ea21d2deba4dd55a2be138b5232b6096fd4456f30a0e95cf846bdaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jRjtaOsVu0wP6cPrsRRpK/MUoMGQKGuJaYnIj/0FBjcTN/fXabF9V9XOxxLSooXx1VJSuFcutPYZG8+KyxCnBg==