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
- 509fba1ab5e1901622f94298aef95f23e39c4409d4ab50295517433883462c9e
- request
- e45389d98c54fd04ce0768bcd374d0d19d5ada321640d63d451980e4bbdd1044
- transaction
- 873892de70c51850744d705b9fdcda3e143e75352d7e11da561f2bf77b8a6675computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46691
the chainentry 46691
- sealed to the entry before
- 09a4c9946176d62f25598aa64845c3ab59eb65500ce67061fcf3fb2ea083d23b
- this leaf
- 6c723c468fa27d8266d4cef98476985e1d452bc9e7d20348313cf5b4069cceef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mz/lKtBSkrx5otftdsJCRhz8G5nP/5o6D74aQFn6rJlnOz47P1n1PE8PlrluFvUtrUmF5wqsLbcmDNE69qEyAA==