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
- 1980ff7a1293661c9a05fcf8ad65b22ce3eaf2953967407a4578caccf82d9fb7
- request
- 6d899b59a5f46acf17c550ec23cbfdc58cbf1e31d3b4a6b7edce686ded4e3af2
- transaction
- da8119c20d2b3c4167dbc0b0692c2d6c01ed30124889a7779a22724340833315computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30094
the chainentry 30094
- sealed to the entry before
- db5f1a66e4fe779fef411d5078e2731f64ff7f9c1804df75a9015c70aa4e2d36
- this leaf
- c3c56b037ac823b744bd2fc1be3fb0e0161f861803f28af5138f2a48b0e60181
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u68+UdYK5dzPcfQRGHF6QEA41DuZh/e91kNaadc1asSIFHyixwnU1kBoWbhZaa6W6rbhxTKQRK7h60UAdxxLAA==