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
- 06bd907c64394a229e708e219ed5a2ee332f533be2ad79446ca3122cf018d880
- request
- 2898e3499b3a8d33329127d548ab75e88c69a055f58d0014c4522f6eded5c22d
- transaction
- fab4a9afeeee6c1defad02cd4cb7c535066c4323845f465303efdd3bc771a5bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56235
the chainentry 56235
- sealed to the entry before
- b190eadd8d149047b860811a45d8851ab761605e5e0d8fea4011960e71565c3a
- this leaf
- 64fb05d68e6c3a9ca9a37f848fb5fcb5e1bb2abec4d9e149f6d61ac99b3ad604
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jddr0VZldSjZuVtHJGRg9G251cvGV+hrFZzk/psw67rYRNqTby73ywUFcnXl5cvGnzaj7LhOnONtkWn6eejEBg==