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
- aa7a009c3752ac392ded6ea101ad71b1d132092e5b9bfcbff032a057d8c132c6
- request
- 17961e35175d07357b3a998b075d0821f42918086ee1b842b0d39d114f3ebb1f
- transaction
- 537628fa3c34f69c6f293f88517ea2efc4011693929613cd0042c68d672689b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40535
the chainentry 40535
- sealed to the entry before
- 0512fa3d8b9f7fbe4e2c7ee762c7bc2d7a54af8371f2c465139e6a23a02143ac
- this leaf
- 09b823891177fc564ce1f308d4f9a7fdb7df802cade89abe0b97a650b97d5188
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tCGAXzfBqjBui2ox2s2BbHNz7QSx/unP1ywK6Hx4py/lkkmJGVUxKxXvuwioQ2/wH1wJWjr3NV5xXEedTm1GDg==