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
- 7bdb1bd49ea2ea17ac3c2252e9dbfef460f3be3633d4bd7712708c3ba0badb4d
- request
- f35bc35fb7862de91e8907b417fc6a5d50730db7eb98b118a638de268c0642c9
- transaction
- af889579047089fe23bacdf4e7c9a31eac5700ef2a795657fa39cccff2676c21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 901
the chainentry 901
- sealed to the entry before
- cceebfc2162750a438ae7d81ced9da10835124a6182ed112068530eca1d66471
- this leaf
- 06ee07e5067918abe866ff0462194045489e9497c201657a92f513730b28c124
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /C/aDdT8ArLkxvVXs8QqhjS7kyOUs6zdr9V4JqjTCTwNRUgu8g9XH05QrnPWRFoVtuULXC2cilC8Rs7Pf8JpCg==