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
- 6a150c5395927ae57c7daed38d421c71b45dc4b67ea46634b70da7670e99171c
- request
- 4e1909ff948c4204b43fe56399fa34c889c1313edf33a8fbada0f9951796de9d
- transaction
- 628a7e2f41ddaf3b3fe352b0857e57459aaf4c9e126628784961ebb3774c06fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65498
the chainentry 65498
- sealed to the entry before
- d07e63dc0c3390b8679c44d61db12ef7481f86c281128641675be87308a2563c
- this leaf
- b6fca5e788ee07e4ebb38b810a769021f0f3c144584cbff7ca0ad90192975ecb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B2sQkW/yaVoFuZ3V7EKop35kDWZA4rlhSkWPVt17U0I/Nd1AMeQrJ6Thy1HP3rCxegeLcGUEM9B/k8F07SETAQ==