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
- 186a6673f0b403b7313630d41f7c89f133ef4b3db59e1e957bf22bcfd24ac870
- request
- e8d2aeb4cd74c59d2f71237a4452d6732c4032bbe741c32d0cbce83a0a28393a
- transaction
- 7e7fe2187a62ff880202388bc9c51bc69bf8b83155c90eb8329825f83847a557computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27210
the chainentry 27210
- sealed to the entry before
- 255f108a6ec06301b5f4f191028b01860400f8aefacb6bcc3367390711d20a35
- this leaf
- c788318ae4e1217435d63ecd2e0953b32a5a8bd7f80b7738928218f85725a665
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OkqXnlnkWw0C1XaVN/bPOlO6meKQISEj3IvlFPCcwak9JcWIgyrl55WS+iXajCss6CjLorqUaCKyn/AvIrtEBg==