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
- 428472d875e1d1061941bae1ab166bdd98af5e7774acce9f8c849c7fba5257ee
- request
- 3e331127362a2e3320df943f685e9c0849f1fc116f9d74feb71f644e612a9f3f
- transaction
- 6fb6fdb28d04e7e7a1346056d0ae6856c44b256449b510dc293f3875940712aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4096
the chainentry 4096
- sealed to the entry before
- e6680e53fa74283f37f95aedbbb2fc734444ddd4db7c5bdf5d043e015f5f872b
- this leaf
- fa3dd02be4da4bc6b75a9c22bef0d4a5191b776884e02c935e561e826b91441f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CJvyjPLOdqb8Kz0CSwigHnRou55FlsBOUi3FeXIg660G6hW69aBduzyk20S6lkZ27riOrYdIZL21vkxisO4SDA==