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
- 3b3ad107410d4cecc3df9e561ef140b1c65e5ac789c3bbc6beecb2f23c6add48
- request
- 1aa696e3ff5f2aeea11239997a5ab194880d7a30a1da20a4acd06917b71fc341
- transaction
- 42e74dd8ee6b0afb6939c2e7c393167266238863720d5fc82cfec8484bef7087computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70811
the chainentry 70811
- sealed to the entry before
- 22ad231c50d108234090aa8f74ea865a70ddb55778390648acf6add9ac84d78c
- this leaf
- 505ff4f76b5dca3fd8cb045f06a96e947801d0144c3926babd13304039cb9354
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 00ZtshfCFqrnckyw7NIYl1WQFynvlDWqAzmlvOXQWyoy/3GzhmVaWJEAwG83XR4Q6ZJl1imIDlIn6VmUgEbWBA==