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
- 38943f9d9efdb3cf4f3a67d349c0313439c5324ce9370f1ad3f5510ff1710033
- request
- ea591558cf371f69a9d97419ec4bc3b316712cc2eb9450d67b155e75da59793b
- transaction
- 4db09842e74849597c7e031e84287a32a89ea62beb39c1918c5e1d21c4932d12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52171
the chainentry 52171
- sealed to the entry before
- 0439dd948ad2a04c3e234e6c0b0ed822a6ae9e989214fee3e63d42162e14b2d9
- this leaf
- 796b9bfe065ff23304b03bee6f26698312350f33b41a7c359c9c31ffe0c96252
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hfvkOekTzFxZJ1dbIl18+WE6WInt3qA45t2xKoEd3nvDtg8hYf/xHDkrT5HNh1g2Lv37sd3ni4ao/aTx4VrzAw==