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
- edfe8405aea66000064476ead5e66f32e02b345e97b26a29bfdd961336444637
- request
- 1af3b4f07c32ce2760b0f26e8f1f0ca2759bea6f4d99927bbab39220951fc186
- transaction
- a10dac25042e9e0bae149f4d96880bb664dc6fd3184fdc8817dfd6d01150e559computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14764
the chainentry 14764
- sealed to the entry before
- 0298a23041dece7d581c99cfabc508c9339de93df913c33a929b54a44ebf7981
- this leaf
- 0f94cd9510c8844fa6491490ba7c3cf8115f592dbf33adf7bcffb6e3bcbfee92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YDGxQwnQ7/6KcS7FH3EiYP4eLS93AJX5dYDsg0fVoA+HLL9bZM02hXrXqJ4cMLbz6GIJezycgeV17SAm8HunAA==