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
- ec7af864dfc2d30c30c16ca5d64872661ec9f76b5f2195c12acc12802f91890f
- request
- f241c5df208e961350cbb7b362a0cfd090cdd7fbdaa150c0900abe3b85590f52
- transaction
- 87e49d0199870be2eb706341dcd1760f52432b1ac1eba27f968f0c897c194b68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54050
the chainentry 54050
- sealed to the entry before
- c7cdc46caeb1a35d0a81f5b95c4724e41418eb5f8e73d1ad9422ae9769460186
- this leaf
- c890af113a1dc2b2f1f8d0a896b94fe69b880005db4f28bd19f9c204f042d7c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7+xXhJ3TEF1rn6PIz9r/736EIe0fgvUFGJNeDxOkl2Bzz7OZENOQxFJsTWfm+o4tKEv0hASWJ24W9HOk0P7ZDw==