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
- 70c2943a3156f41898f8f8a730c787fa6d65ad9530af8e37db8c65d9582764a2
- request
- b1494aed4355394be8b91375e0839f49afcc3e0ba4add296f9772e579f45b34e
- transaction
- a211c2aa742a7a469ff02676c1173d5cdcf7b4c3afd670f2d3ed10dcb1959588computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4901
the chainentry 4901
- sealed to the entry before
- bd3fa6a2e7460e038856244bb6bc3e0ab6db614529e934098b889ebca0e03814
- this leaf
- a6f4450db19e59639c00415440f0e9522539adf9d264e4a7547ba2aabb39044c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IzTpmE/7jLiTnDHeaZXAjR6069w0dtxcwVr/lzucHIgg19IASAZg1atQXzJw0wVeBbkiOaniKKUiNjHdX7ieDg==