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
- fd4087c4401332107b4e4e3d03e3a41a5ac5b22db88f0335bf1734f81eebdd2f
- request
- e4b90848fc4c3d8231a6db627caef62bb156f8934019e70d9e79c786e84d02ff
- transaction
- 6b2adac2f2c03e278ff66f5df8f0712511964b6a1068875574715c862b75f2d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49199
the chainentry 49199
- sealed to the entry before
- b1da7252128971ccdc26bf58f8317892af26985374c8058b9404387276ead374
- this leaf
- dd4ed6e1c671a7c6075d5b118839be2c59cd5ea454e0fe3e0afb7c9b17878f2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ND2pQJRNzKHqiaMJSp7H5JLJ11NHHXK/I8PXkuwc6udbv0b67+yAjmpkwhuLohYdiqGh2TGCCdfeI6cQ6Xj9BA==