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
- b7868c88f9a3a4ecdb3dbd5cc2b41400f3bd369051d6dbc6831232b4dca3511c
- request
- e6a4e3e4f82983a1be8b96c75831cba93f1a297876b7230f7f33a3a226343bff
- transaction
- 89852c93faf7940acc4b9b9031d54d3795ce51f25e9ecb4d5abce8686055697ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75658
the chainentry 75658
- sealed to the entry before
- 70160bce4c30d3d9a553a950de3f846cca898c416e2723a99da6f50ef7a3468a
- this leaf
- e82ab7a516f2335de25e62c10d50604404ebd8b6f12b06816e8fe4947b077603
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LV1xI4QtCsFuOb3Nu42qPfm3DZaXGO8cw3ybxUfole0FR5ukQRmPQuFhRC8z0VsfwHVV19OViVzFhNG83xz/CQ==