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
- 2764d8a72ea1808ef8167b7f5eec88aa33797d6b5f569f300f694b13133013af
- request
- 845090b8994692dbfdfe3387a59f6c2f682cdb1dedd53dec1de9adbe9073744a
- transaction
- 8aefc239812159c9235a59efa4bf08cbd40df962eeb617b41b179da865fa2333computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20189
the chainentry 20189
- sealed to the entry before
- 58c36173860678e65baf01733c44dfb94f371af943b795101d157531d35839e5
- this leaf
- e88979095c68b03863c31aae7074658be328277433a5f554f5138c1ecef1bb0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pyANHH92zpXshuPoUEjJXqLSGPvWWAZO+p7A3Mc7lVGqExKKRhmxPeWI20Ju/HFMAtRyZ8r6SuKjPT3FjYtaAA==