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
- e16b7c1d1df550eb18774403fb275714ce880d7da8c038145e430371893436a7
- request
- ab746f63259cd5bf79cfcb83a1587e0c4cb79b7a294566d7d533a791dfc11af4
- transaction
- 7efa6272a559ad6bcf3a7f3194bbd23da6535ccd5a7880d9110fd4162fdae6cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68856
the chainentry 68856
- sealed to the entry before
- 95fffca1bb340cdbed3f59ab2697ce804359fd7e06f847e319b1db5911146672
- this leaf
- fc5624467d7ec8f8f6421c2e031ffe839e193306c6eda6ddb9936920baafd649
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C4iF6oe0Y7k2GkaaL99OUWfnE4r6JEpD+SekFDwyEKtGS3Bz7Bz6uZe2LEvrN5/01q6TjXtcqMg+B2gR5qQaAQ==