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
- e03eb51a5f609f43e553e16656303396c0e906ba6845fe46c4aaacb862c59c99
- request
- 8088333b2ca67c7bb2cafaafa7c8bb8978b6c7ecbdb9d4f5f54964e1f3bda92e
- transaction
- 4fd94a488f08348c4100824ccfca1cd10925f5f93fcfc5d81c057ac27de5d908computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5938
the chainentry 5938
- sealed to the entry before
- 0dc98ffce8cbb6f444ba9f08074b5839cbc20c01deff384a2bd25dce82deef73
- this leaf
- f3a89a4db0e41c257e7303bb3eca17e0f7a4c6367fc145afe0c7e0c5c96e1f82
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SvWlrD41PXEvRxGnVMHQARxOvfTu0AS1WeMW/gUXYVJbvfgFbHKW7fsJLnxlcft/IuoIcvvXOCct8WEqogfuDg==