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
- 58c7885e70d4528443dfa3189f1b8634a68bb6085988ee69ff6a1f3713b0dabf
- request
- 0b54296b05f012f8f3e7158ebd89dbc70a58da341e4d5eb46d392ba26d84eaa0
- transaction
- 6dc42d8695b869d0b48b48c63c4c2924ed714ff0181ddd4ce31fc32a4e5ec560computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71142
the chainentry 71142
- sealed to the entry before
- 0e9786e04249f6d571bc3b47c03946ac81c9ea096382446883eec969b452e1a7
- this leaf
- fabda006f5113acdf28470df12494c5255bd35f02bee78d03fbd4d112faa0d82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5rKRndGGUBXQS7DAixI6gvEKyNt1tqFdfBXE/GOhBSXBXj4Oe4Vn4ikl2gGmaXxF9xeloqtMnGJH6OjIbyM8Dg==