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
- b384e4974d669caa288bc5e601f6ede07adcd85bb11c966ee0e6bfb4fc7a4f42
- request
- a03c9caf9bcc864d6175de7395e239c92628f2c2be3bbcad86dbf9e6933742ed
- transaction
- e89e9c47cdadef75e00b78a2049eeeebda2fd7f16f15a150dfdfc6eb374aaba4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54008
the chainentry 54008
- sealed to the entry before
- 9890f41ee399097a2a06876c492ac62c4c1de39efce83c0079bb147d213e8a2a
- this leaf
- 53563547d4096bc6e8b63205c2395a266e9ed52114fad20dbf6ac7f5add35e34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h8U9FSQ6xzGX+6rnwaVjr0Z+ZjBL35FVSWfNhphC6YKgzjGZPtcc6dVJtsll9r9YOYOd9/+pupQSM17MSMn0AQ==