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
- e6dd7f4d23dbd3bbac81c558ff000026e5ad79226916f31d384bf6d8b832c16f
- request
- cff417d864e6fd480b2aea3ec95b52c074b87117884db2def8d79d300a25ca1f
- transaction
- 7a61fffe9ac76a3d33ce933598cd207c98abeffaf8f43563941692a5570a903fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27329
the chainentry 27329
- sealed to the entry before
- 64f6f2d724044c311d0bd76842c5d953efc81241467ff1fe00bf5daf23ba5526
- this leaf
- c254eb8eb1432f4b7514e6fef5f2d671a21639f3618ffe73c08eae8f30984e33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5YDCDij1k+opjhB9N0/pGefUVlOinJOAlZp5x13MEo8LHCt8IZoyp0Edj/t4IyPTLaqht8oIfpFHxfBqDqQwCQ==