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
- 40a75f6b80321fd93a23f04360e63db1d4c941dcbececa188ab6a589c17653df
- request
- 9a4ac71e772493988c2807f3211f04d99ede0c94748c316012a72a59cb76dcb1
- transaction
- a5b652e27e258b77050bbd3f0a2d130fe2eefeec9daea1c56fb70fe98afd9176computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24912
the chainentry 24912
- sealed to the entry before
- 9a307fb1fad9f058c77a318ebdd1c0c31b79d6a31ac97db03c25d904d5f8d35d
- this leaf
- ce318afce1caef5fdc5f7a857282b011d86a767d93b9fe8fab2564077b8a4e8d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UNULcvzub4TNGT//h2xPZyk7b348ak0EgbcRu3Xa9LCj/VfCqZC5Sd/tZWdFB5yz0INYpmbkW3kBx1gmB34MDg==