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
- 6167b6734a0dbe14eae9e4e1ee146829cd7710bb1d181de2b1e00992a0eb5476
- request
- 6fde2d2a391e764aa949db6bf3ff492168bf3cda7c7906b1ec207fa52f4fb498
- transaction
- 0eef71004fcb35ffe0eeebd92ec66ab3096113fa23dbe4db50d00bc56fec5389computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33312
the chainentry 33312
- sealed to the entry before
- 406e6310b97c2a89b39b7c640f143f5b033e42e2a23175c1e91d73305c186d69
- this leaf
- 3f2121ec899c1795ae82d6a5f9c0c49350ee7919a17294509e94cffa706fd9f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ldm/b4gUpGvEENC/fflHHN4tbpvPQMEPIM0UCBYHG9J2e6+KqW7pRzOkW7egPrc+K51iIrzrKKLGjPYdey/iDA==