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
- 67f2dc9a1563ccb66166f1b52ed97898ccd3d33d55bd828a604204f5e7590b6c
- request
- 46e7786b756e04ab212c2dd6b61d7943fcb73f51c3c968f56f7e0256da3c4b27
- transaction
- 017576a65bce58bd8fafd92033ca80353964681a598f98d9b8cf604037feffcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33278
the chainentry 33278
- sealed to the entry before
- e7d683147d54346413fc8a24128c99f5716ede3222a1279f988c739e177cdf55
- this leaf
- cdf70135994c6edcf68da1c92f7ffff28bff3e039e09e95edbbda14a919c91f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E3nB6qNkl2rs9g6mp81IVp5hvuX6NzEgcpiz+WFus5PsuEgiaaUueNpLCgRCTils6SgGpCDMinQAl50L65q/CA==