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
- 4a21bdffa18d2db6f1fcb141cef97613f3fb42ae344eb014927269677b631e3f
- request
- 3b2da87ece77919fa80b487f4bb5f4d688f155ac9505340a86cf260bccc78c3c
- transaction
- f004af884551358001ca9ff38199e384e125d90bae6b6ceb4d29c2b7010f4f28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69817
the chainentry 69817
- sealed to the entry before
- e99b878dabe95581a6da1de5efad90d40d92c62e7d0cbfcfbe3627f802068cae
- this leaf
- 3fa75a8e4ee4c87068983a459ae61435b2fcb22984e719e4391e0ffa59cdbe82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /g66gCgS81RyGpYmqVBQwPc8h14oAu8RM+KRwNyXxWTxlRmCDoLe643C55xCuS17vr48cQqb8YqAeTJE0pOoAA==