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
- e8a24dbe583c715d8ae233d8aed9fac981a5879806fb0eafe9091f09bf283495
- request
- 3140b9b5b5f703d9bd3691e10b444d640ffb3abf42c847fabaa1929b0fd6123b
- transaction
- fc3d3c53c7c2192eb069ee118cbc5d8e4717e17008fb1318fc5c522ba35e8140computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73743
the chainentry 73743
- sealed to the entry before
- a36582e8709a88841883a02197152fedb3e80017d0acf8c4cae495b442013756
- this leaf
- fb09bb500f73f2c8938b399f6a5523595ed53571edd7d8e12a18a63c39c75b4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lKBg5EDmqF4SweLSiuwNIs/BI0a4B2YabdJVK5mfSh7cOBbBRO99KLDAli//QIsiM3kH3V4MjH8vBnKEvMaLCQ==