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
- f809f13ae2e28b9380b5ea79f006756fffc657758088be9c3d91cbb5ffafaf60
- request
- b0b158e50ec0191a730fd49b40fc9327bea535064f349d70120e7eb53206dd8d
- transaction
- 4e111c5747386a39072b46748bdaba0b825522269ab22f954a492717747e3000computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45060
the chainentry 45060
- sealed to the entry before
- 6efb79217f6e0067303ccfe7aa9a391c66704e343cf677c1ca3187b2160f4070
- this leaf
- 46fc7bbf7ddeea9521fde9171408b7d1c068d8375f3450a7c8859753dd9922e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9hcv43KGJQMx/dDggwAfIeTlbF+sQ//ixfireqdX/i9JCsG/ab3mYGmLJeVu2AGMVTyvwaGLTOkrjIsbGbHeBA==