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
- ccc3386dcecbb0374d3923be890aa9c441ecae15a4c3424dd87d57b1474f59e2
- request
- 57cf73d06bdc3bf27d3cf239bf54d02d4c5c5318dba4d514bc84b03aba9cf4a7
- transaction
- ca6cbbee8578745dd32d7b2f1f2e94e9bf56caa7799194b6271c1ef50e947753computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19253
the chainentry 19253
- sealed to the entry before
- 0f95b71627db25c98e7950b8a7ca8ea9ebb8beaedbded0b2e72a8e87c1988cda
- this leaf
- 57071cb17cbb500a97e36a77cfa931d99d696e72c34c2202943f5a5c3b4d8aa7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E6KBTWRkNhprEh2cNYdcFvYyI65fT/YAj7FNIxvE3LnH5TecN6eOKTZ8N3odf76PUBXBB+qvZDNtG/837JWCCQ==