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
- 4a7db018119d46681e951edd64f41612c4666cc63e92576ce83784010305ad3e
- request
- 0289b9c58eaf4e4d601d661f584d1424c19a4e95eb17b2fc32406da8bc5ce617
- transaction
- 0cb2a23a09cc6f339ad8fa39c2657db6a4bbab3ed72f56e4ec06ae3d7f59d809computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25874
the chainentry 25874
- sealed to the entry before
- 6a98b112570131c7b540d190eef01070be9af786d3973ce3adea0210011ecb77
- this leaf
- f5255c46cd5fe7db3c370416b229ddb6915fc646be521c6b807eed7db9c9e3c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VLayifeRpMIGV0gDP2g7ed6c965AhyZbjy++pHwF2QeahnS6OzjdX+5oY8zkAecRI4AKONwcoL7KFtma8o0pAA==