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
- 7dcc6373d023f6aa8baa138bbe72f4665e71edd66fb3c9a40a27e19a25b08136
- request
- 1451ed66585ba6fa6c9dd04aa93e44cf00b629ca0126a2a6325b692626624b60
- transaction
- 784b2d82af495166aa56198ee1c0de637f34a1ee7583b628c17288af48667f00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21059
the chainentry 21059
- sealed to the entry before
- 058fe9e2c0d5df5bff7acb3bb83a3863ae1cb8cfe5ebbb09a22569bc3489ccfa
- this leaf
- b94e73b3e8c6c5ecd2368770d37365f959b105a9df124874fd09a19f92c16f23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bBhKvj9+128UCoFu/SRSGbIWVHyc9FGjYS040lgOFjKnjKftv+9R8QW8zOLYz58yHUt86eoT9WBATXwXJfLiAA==