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
- 84569c216da589f001aef5ec5814ddb84c340f29b58a1d080a317c3520f2609d
- request
- 38a1ecb81d85fa6e34d648a04f30f7e77c59299a4d6c42a192dd33277b7b0d3e
- transaction
- 5461979f56a8da6a5f3bc62fd1cedf450ab1bb63c17942edfcee9fda4d77e870computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20999
the chainentry 20999
- sealed to the entry before
- 4a2dd0f8d76d1b65a545d0cfb99a7e32e3a85d51a7db49b56a53adea21a594aa
- this leaf
- c5d71ac43e8091a6e1d7027cc955aa4b284902d4e8b8ef90559f0d8990d6cdd2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2I3RHpGDL7N9TZWjpuIZX8eX9FZRsIbJzpTkHOqXi76HRlEy90e8mf5WifzbxMeEkJ0FOYz7X0re65apTfJ+Cw==