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
- 517312d04fb307de6a0825f1ec54a33594cba04e5e1049f9f75450ad6840ad3a
- request
- 291a24d701fa904daa73a14242071c67808bd4aec5515b00b1160b18d061220a
- transaction
- 601c18834e372cea9b46471329251a1f7ebd81ce07071d9c95e60721edaea493computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24080
the chainentry 24080
- sealed to the entry before
- 58fa69b086c4811d671397926750077c0acafc110003da4023111106dc9e2cb6
- this leaf
- c379ccf4983f33f06355bbcfd5ed4e2c87f9abcd883096095bfb04219fd0a701
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iS0rmL78LTVXFV9bCek44CtZ1rHie8J+rH/oZc/z7r2qbrEPlmJSM8SyTFR8gKSRjREgB0yXBZWnAdM8g7PIDg==