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
- 3fd29dfa4872bb59033d5d4c02a81d319d356ea4098c5925b0b3aaddec260d36
- request
- 8d7b8a1a9f3816159e49b5104c59063b5ed0cce73031365327a1c8afb46ba135
- transaction
- 012c57a840a9482a3da5fc1b721db303bef0ab200590e787101fa197c8da71f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2025
the chainentry 2025
- sealed to the entry before
- 5a5f6ef42a94fd8846d641fcc8a3028dbd8f70f94cab6cf4368d0a3df577aa12
- this leaf
- d6a1fc5188697e5dcfa6cd1ff120da89a5cb2f48d15f026969bbcfd924920439
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NEeVw06r+WqGBKVjmX/RhWTb94ZGHJO08TwdT9mE8Znn++d3LAtodkpt+5kTK0hTHTaYhCZ4DBVrF+CL6hvEAg==