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
- fb8c26218ce04a162b01a714c4a4ed7817e3f141190bfb94d01593f87e51c762
- request
- 63111b1a7e68b9cc6f22c7e487494b2ac9e877c635ace31db395b0c3fa5f0d09
- transaction
- 2ac86cafadccb74b0011e4dde4b52aff61d04be4d0254a8f76a5bb646f8b5672computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64860
the chainentry 64860
- sealed to the entry before
- 0872d8c051b4ffc0f944cde2b062534f646bdea4f432562c7b671d4b0522a71b
- this leaf
- 68eac8cbff4c826f5b3efbfa1478b38484bb5550970680878b42865a925b5807
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X8H388DXBKHQznU2cBPglPEfJPxbmSCfACM48YDH27tc+Ky9giIzds1shV96hTt65RJW8Rs0EPSVCATtKxF4Cg==