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
- 9d4cd29338f57436ad9a4bc1dd4de18cefbf09caa60092780bda68bd275778c8
- request
- e8901801c1eb7b887aeaf54e85c7eeb7e0b702a90ce77d76abce0563f50123e9
- transaction
- 9e3b2d2ab66359294712447313a8618315322ee329612631b2fb3c3215b882bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 581
the chainentry 581
- sealed to the entry before
- 40902ca4a591bce075abe3e4cb4b2a3a89e7b516a72013b24f387a1215e4855f
- this leaf
- e5008c3d599192462268c097e557d36afa3d6d64b6578c983551a084bee65313
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AA4UqKTRuo9YgllC/AgVlYOVnZK+S2KCnCMuMurLAFPKtrRRx33L1UeyjfeLp9qK89s/zLDEPCxC4TIwg4/9CQ==