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
- 3a6faa12fc3732bd246d477bbbc3abfc005a26659614b30e4c3670a2b0f5b08f
- request
- 4ae5a056cc3ae6dc61b122257402845a9db9c9d6c2488f92bb84ce93b999eb31
- transaction
- 03618e73876b75fab93869635efbb4b4ba103ed3eea5a95d1c0efe00acf2c49fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73195
the chainentry 73195
- sealed to the entry before
- 43ce95b4da160ea44718ae0872c05eb57d5cc5e77772a266fc96c931c4030757
- this leaf
- f5b8250306920390784812021765ed4022229a324d90f5f6c987ea3e11973135
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h3zx6E3GeY16/1+hA2obRTQOCHO+QUnVn9NXexblQ81ILHDw0KecoylJVj3ImycOoeYR/QWZCHZ02BH5DFYMDw==