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
- 3205d8dfd431c603a37d2ec84e4806edba7d44fec3e6ea1112e22e5ca7b3c968
- request
- 3f98d13fa5cfec5fc99481ddca0698438de0e3f413a254dd8e4fd4b5ce49d296
- transaction
- eff3e151784bdefb478dac06785115c667415426e065a29c47f1dd769fd32176computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54860
the chainentry 54860
- sealed to the entry before
- d4d4db3ab5760472619c760c8007be1e7e0084300d7fb369697bc656c0b811ee
- this leaf
- 00b6d92bb1eef470bd389c8470e7ee67d5251714b4ec8b29e7f31ba0e7089f3b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4P+XVYE7kv2DiPJzpumjx1p3XsIa0Mia/+w0kuyRhPYQOdMqGn6nMd7RXUucd1yb2HuSjLzFNulwLm5vJ4qXCg==