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
- 445fc030cd2f95f40fda1b7ec6c3512f87702bda274fbfa5d5b53dbe03adae46
- request
- 84942254b284bd227a9c72167a6db1b7b5a50bd140c27d3a26a87b3588998407
- transaction
- fefd16b6ea5575576e8922e477b3562ebdf890ab46c1781d2f08030186d1aea3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72097
the chainentry 72097
- sealed to the entry before
- 3da223e2ba97a5d7955b193d76a35859b9530c2597114ba657d83c621b151eb8
- this leaf
- fac0a2e9ebe4781318dbd30e4c0fe3dda1ee916fb4f9389ddcfcdf597f4803f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A3QdDWeLUfgZJT1oPXWOc5YFInQmmB+/mQCMhUBP6ga24fXrNP6iuhr5nG6j92exufLJQ60BS71N2fN7sxQmDA==