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
- e1289399c71310386e495f3b02d8762a18cbcafa894c15b6904c7f05424992f2
- request
- 118d9cb6443eb2babcf393af19ad0bca718b931230d300b304b6cefc8fef8155
- transaction
- e7d8e248fa8d080daae59e4bdd7d6e31f39d2657018e856731e10190e0569bfccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76040
the chainentry 76040
- sealed to the entry before
- 1fafa272a820892742fe08d2ab2c4d07a679e73da3861df62c8d1927e28b7648
- this leaf
- 1eba12593a8e99ae7f651f58e2195a8a8eeaf33d7ec85a34cd9ef72322506ec7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RAfx5x9+FtU1rU3onP8YAtsgRlRR1tN3VmaAIxyYzvUNcJMG7tSNFlsivXH6k8YAyFimUBEvheyXbHxbMh3+DA==