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
- 19269a75cddc4b6aa19adc688764e774e76f4072a0de074889773e0342188f32
- request
- d80034bc8459714c6ce1582d0efb8a3a7569a362472b343dba7f8f685348dcb2
- transaction
- e87c006cd01ca3b8cc204c6e21bfa107b9b245f70d3b5a5503cba5eb70af68fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46
the chainentry 46
- sealed to the entry before
- f4b8f98aa860233f1e2c353957a68ef60f4450e428aca967f4c6a57ad2a3e96a
- this leaf
- dfcca7426915c2d7e7e874fe98a6a9d9f6a1a601285d9f5ceb5a7e034612f44f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3SAu/fkRtywkf2tlyU9+Bg4JayjZXG4gpRE+Ddm+KXvBSsKjOstoTOfxogc8n/MzGIxrViwvKinjafft495DDQ==