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
- bcb458ef5025c66a21d78899b819bc6c6120d9f704223b857cdafac343266410
- request
- 91db2dda318fe10d08714789f72618e6d86cd4be5f9fcb15efa2d518e13d8644
- transaction
- 4193c28eebbd45f9c820d3fbadc89e72eb2977b48058862100b0ce2a5e4a61dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70396
the chainentry 70396
- sealed to the entry before
- 40b4b5458303528b2d6d575fe96e0e237e62be3045f1aee9a58c0311428c5834
- this leaf
- dcf138bc6366d0cab1248e89a3d768576f19058fe203551da0ae4f5e65562955
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /FWaiI8Qd5b9TDvDT6ttj0O2wl7KRDxrwDRSePG2EsVnCOIr4Bbfc7ESJ3Ze2iMHGdtq6ak8rVU7eFulpoHDBg==