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
- 22eb09ff21c14da22142af6ff93dbb278afb8527e61a0f4b4905bd01e338c533
- request
- 0694d32f581c50c0f1518a5e82cb6e8efddd7fecfe704c72fd21c945d8dd58af
- transaction
- b92ea0ed6bdef694cad62f36d63f30d017abcd1c3f9e10a8bb65669346401840computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12880
the chainentry 12880
- sealed to the entry before
- 09a25ea71cb7beddb3b9e12bd03ca114ba27961404a980dd02bd6221a91dd119
- this leaf
- 35e4e5ad5ef0661ff46d7e7bf48a33ed96e222567bdaeb1aa029e73493c6aef2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pS78I11oD+nq8gbyzVP3n6T1+17dWCJd4umjia8FOCpFGlOEeHpwLcRLn81Fq2OicKJeYV34mR9mTmVjcE7hCA==