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
- c09c659c0bf00f51ad5ff5ada40b035c95eef23f65e0abccf981a1cc12c263c2
- request
- 6d37b79c7999ffa10299f11cdd139b39b1e2f9d1276bcc6c0e87c4d1344d5b67
- transaction
- 679d497e4a799b9fa552ff952846723aabba8aa19d1f9223c2c341a29d0b40c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31530
the chainentry 31530
- sealed to the entry before
- 745a75818a4f3f65d76ccad6d86cf5b4164e856bf271c08a35309f4c4e976dd0
- this leaf
- 37d4affe5a2f6e65dab7d52bd8faba7cc8fb714f136ec6d17b366992d22db62e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jh9nj6sl30eZmGBYa1wcYwlQFRuGXG1c1yvb2lUUdtmTv8SyHMnq6J5amR63FBAgRtBHnKB70uXemigv98AjDg==