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
- 4687cbcc2a928ba11343eaf4bfaed6345590f6c953b6053c16cfbd01a1a0fb46
- request
- 21203a3d7763bb75ed7b12dfa086f3140071132e6f32b58ccd3f604bca690763
- transaction
- 6978382e699c38f3492dc7cd6ecf9990a271242bccd75416a477b4e4aab5a4f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22009
the chainentry 22009
- sealed to the entry before
- b978bc402e96bb582f93f60ff4a063ff89762f8c81b8ed55acb5be5aba3ff4a0
- this leaf
- 9dad40d96eca969fbb3284d46936fcfc1ecc8b791f8c001a678f20a9df4f0bae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9p7SjxG0PypAbVFNCxgyJ4iGsO/apeBQvb5UkJSPXq3jjvUou9FtI/gNvUpZAyuEQ0qHgjfk6G9+M4tfKcoqAA==