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
- c13302dd0abfd0d3a604c4c33d58f2de7fb59d0a4139462ab8463ebf03163356
- request
- bdac68164dbce2320539e5390694e9415b2610ae351d208d8f35c2150efa61de
- transaction
- fabc48d7ffcda705819305a8d4ec9c46f08488ea8707e5f0331b1c34515ebb83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61278
the chainentry 61278
- sealed to the entry before
- 764f14f046284b979f79b7ed21938122857b9c603fb5974a99de88b7e8d1f77d
- this leaf
- b0ed5cf60d6e80514cb92e91d0ff9fd976e49e4c8e07a1f9cb2a781feeab248d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S2Go+0s9IkMdyHLeAZs3LZXaS0MkFxCJOboRy+Kpp68Zx0yS4W8wo7fwA1uBzG1gPw847g42cU17V3TvREWnDA==