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
- d0c9966bf3d142a004ef6043871fc1062359d512e728afc4e38840e6dfddcbc7
- request
- 176957186f66758a6f0f948288c00c777fc4566c07587ba9f0ab951fd95006d1
- transaction
- b54ebe55a1f4947a677425303e07f5268931d6a0933c80c4126fd312267528cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2290
the chainentry 2290
- sealed to the entry before
- fa7b0af484ef4cb661bb614ec479bd956d1c39197ae2060d7fb44c674e93d323
- this leaf
- 31b2eecf9b44ff9d4e78b9b83d471b6c0de2c24fbdc821382797aaffef30eda7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FTERbLSMtmMXoQWaqsKR9kLCFiq0mvxopQWznZMRAzwvWsiKPLS+0zhPoESeHG7LINVHJaYuIirGzgj1OsIeBg==