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
- c8204c5029b1adc1e96583e5bc48a25ba5c216f3ff6c4dffb5c2b2c4883e6cf5
- request
- 142dd1e492145aacfba5133c045f9e4035527240d806ec9b83f1bc07c9ea7f8e
- transaction
- 9a1896f13e8037add117aaca1eccaa5bed7ac43847fc85d75bf8ac774fb0ea17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76031
the chainentry 76031
- sealed to the entry before
- ce89e3bb38617f6242842eba2f3a0ba487228afc8b47e97f88ce125b1c9abc82
- this leaf
- bb66f300c6f26d8cbfcac9254a7a877480f841fb57021c83ff9984a712e6291c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fwIvfap3KNTHXUxJoj2gJeMWy5lVWVyM6t6wxiP4E78XoPcNZLxajWLmVKJA1sJLXrO0iIO+TM7hEnw+S7u0DQ==