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
- 9e819dd67933bae8f39fe9d6cbd540acb036e4572ef61473dc58b0609c9bca0a
- request
- 8606050fa6d296ddbe83117a44d54f71f56936f0411c4ecd0d6aaaf62fa40bcd
- transaction
- 5832372efcb2f72bc77a775a01d0875311afcdfe0b4e6f6fe03ee7ccd95b3388computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29697
the chainentry 29697
- sealed to the entry before
- 7fc4db26e01d2db439394020b92b484d69ceae04a5ce93d80a13bc3feec297ec
- this leaf
- 90bfba9c8a4fbf99669352c3d9c001d24af03bd4a0a7fcb9c0ea9b20a2957e23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MwxsqZ6jm1DkoRPHBaCS0NMaKFIbztfDW/fjKxMuJusDlZJBkplPx31ldZ4kGmNrW4/v21Cs//epFpXhC7T9DA==