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
- 6735e76fe38dae86a0f72ccd3464bcd2abe0d634b70e410b311bf0a352e504e8
- request
- 5f33d142a9313d8708e1bf9a5f1bb65fb7a3c2b57031b49d4798bfbf2967f2fb
- transaction
- 38295d6963f16e21910ce55320853eb2656b3334e52fbac3ebe710c2f0a55fadcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8998
the chainentry 8998
- sealed to the entry before
- 955d69bfde46e279401012897a5e85dcc4eb319ecd7dffef2f3b6d8284e6fc1a
- this leaf
- 2fac6a64b18ff5e769d49176ce82b46847abc8beaba9e7a88fbd28bb9d62771f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X6Jng2oF00xP5IQ2G19hK8zNm3zwjoa4SumB7ur+JZj+YheGrcVqLggh/ZSrGvsIw0QRe0NFT2aGTT6D7Z14Bw==