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
- f2478e865e512bc74ed7158eeffe08cde26eb894ff7679be864c33013e20039b
- request
- df8d6dc8a2553e4f8032c0a4ee9acd7c6bde734a3ecf4690f18aacb16ef5ad80
- transaction
- 86bc76f8ba9f72d1eacf5e7e90379e99ee1b194ab08d066d673a705900e6c427computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58800
the chainentry 58800
- sealed to the entry before
- 435014906b87648426d86a72209e1371b711a36447ec1e3bbeca2d211d6563eb
- this leaf
- 8cd08b46509d4f4df082cd5f546d46e95c87dffb6103e864eb72cf0559d863a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 40CXyRc+nUcLm8pOnSB2srx4BD4e7a6NyLRewPaN3K8upaf8STbq1ept/ONALw6t61sNdsq7Y1BloeyZho6FBQ==