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
- 80892387e8214107b1c9a3a86b1c76dffd77509a0c1c3c8b72b86801e235f38b
- request
- d226a402deb8cd71d15660997a2fac731e6ee6191b7f9e0acbc434287e3396a9
- transaction
- 8155c87dd2aa0a6781b36ce0ab2c8da26020e74127fa8b1e43aaec048b96eef0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40486
the chainentry 40486
- sealed to the entry before
- f3c542927abcee52d9fe4109abbd778382e7dacc64b5ac8cf47d6ddad167d8df
- this leaf
- 91b99fa0bb74f308c323a137cd41fd18ee57c975a15d502cc7190255cb10ee30
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kTOPMZbbiAaEkCrwsgJxnJHTvKMAhRcw2qyHQ+Bnld1FmfX9rlKgCYqT7NwlJic6zAARKseIplFehJRT2ZWxCw==