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
- e65de51634589de45a2b23d7cc14185e665d8c246bef995bb24a274864d6cac8
- request
- 1b3283416801e3cb42001217fa0b3cae29d5935145133db85749a1309003e01d
- transaction
- a982cdc321f116d99ddb2421d474636cccced39686f2d3e8801a72b2a3bb9d8fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27167
the chainentry 27167
- sealed to the entry before
- be1441228c87b66f6548b73e9de918f4058ee2c66a165912a263f63cc694956b
- this leaf
- 05012130dc04c3ce1d7dd25c30ca63e99de62772542ec3db8854bb7ee7b90053
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TEdWybbiP+E2iwm+uNui+gCrCHFtJkNrH/fKC1bFWbxlycz85Ry9UVhH5N/Cq/2QH6V0vlFEqF6a5a58Ma5pBA==