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
- 5acb11066637628dbe5e8d6e65aeb5352fb090fc1e201b27e26e425be94ba9fc
- request
- 6b7355090ead014126e233c296d8858a2959c955373bbe58d4afc9287f4db36d
- transaction
- c0c61f28755fbc56784792b221712caaf438273bb21c8d56e3d6cf8ff8df7ceccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61525
the chainentry 61525
- sealed to the entry before
- 91820fa7750267d31c415f533df2768ca8dd662cd44917f97a3b8b22c08f03c7
- this leaf
- 0677e08fd8147a109b4fb6dc163ac577614da7920e41f0c39bc0911d4ee9a4f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GrF/tcLeaBcl+0nPW7w6ArfpKg1bL53YYyHV+zM1qDUsNjW5V1JWm1AVNEm7xHxR72nJqVD1kh9z6lb03yERBQ==