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
- ff72bb548d7f5005fcffe6a063ef58ca796828ada53c53bbf7186d9b0d20122d
- request
- b6938fc80d6fccaeb12c626a066bcbf610ee5c1f7178e408a30a5533ddb9e180
- transaction
- 0463e8f6dc1c56c87501eb468f1d38192ec5b8fc7cb075bdc0fc1586b1135e50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1385
the chainentry 1385
- sealed to the entry before
- 818b04404cf705fa3a1ceacac7d84d5d5d8e32b32095c08d99d3bc2549e81a3b
- this leaf
- 21fddb500e757116df092b963c9790c6c3ad5aac8a8ef143eb09ac1fcb2537f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a37jhpZ2addHD2r9PWlwmbbIvHZNjjmKYSHZ9zh+DGBU0xXh8EwCB/xlkk2LZASQ7TvwJ0W1sVtpJ+jM1/dlAA==