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
- 07cf0877d3d46bc7b9c6024ec0afff0c43a3e9a7542a9c4ac42e458b93e29279
- request
- 3984f2b4c91eedf11b0abc644b876c899ae3c6eb72c59eb136d2e18cabf99a0d
- transaction
- 908fcedde6913ac901659240139e42502d17408fef22ea257d21caab4d3464d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68747
the chainentry 68747
- sealed to the entry before
- b44b8bfa1fdb4b687bff885fbbc57a3c7f18b25c0fbca6957ceb1520a63398ab
- this leaf
- c94e96f998b661da1a71338393dac9eed2a628e5ec8bc0417029ace5b2966f1b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6l3UrVzn1VkWr99R1I2xIusy6VvA39jDFbLY2SeQCIiqvCbIm7TEvG7nmQGTue7b60EbNnQDj32RSN3gsrEKCQ==