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
- e45d85ad1a958f335d809699985451230edebb4abd3969c8c1791694efa90f38
- request
- 239544ff91737afdb4c1afa80be8f4883b26d13ebe6ab07c0a86ebe8dab60a1d
- transaction
- d283bd7340f79c7020a3a3ea28e165bc80feeec2c144387bef21d41297ae09fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56375
the chainentry 56375
- sealed to the entry before
- 3f95f1d197c231fab5aa759e8cefaef0d45b446a261e69066ec1e283705af84e
- this leaf
- 9b7c524a0b28cfc68ccb3b4fa79b0b24f4578109ec755c58ce0b0925492ee24d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xe56SVT5gSou7xYHcGVtzlkbniuKVixJwHWd4sGMVsZecY7VDGTZzAHP6Oaoeui0whofmUQr1K4bLHPYblM8BA==