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
- e3603d7156d4effc7f9513405dfe1b5f3d55dd6cbab16fd9da425cf6c61a0367
- request
- 13b00aa088c121d57627f92ff0ca7f2458d8a60f0cdee21ae0019b15823c1b17
- transaction
- 08f04f59c401d3174975079857948497860f7f45f35e2454e29867dba811c6d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23901
the chainentry 23901
- sealed to the entry before
- 5e6ed4fb32784fa82ab5822f581cb09b0126dbefa5f7d47ac02c2c99b23da8fb
- this leaf
- 515c26df382508a3e3596ed24df9d574a94f617a43c12c95a71d40648ad94ff6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4XL7eI0Q1WRgbFWqQRW7iHJgRN1l/MyVD1XcHWmVsY6sFQw2KWwzSNjVUlqUBMvIsQB1uzM4n/fhS382JoNlCg==