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
- 8414b385c3f3fe2cc457f255c52da8f925b1cdcbad128c70d9559d553b9c173c
- request
- 3e2843f9a88cd106dcdd2474c9630913a725d167813e0ca759f4d4281fe8523e
- transaction
- 15095db605d73ec8ef11918ac4091aada75f0df806ed280ec46ec7a694c4a6b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62073
the chainentry 62073
- sealed to the entry before
- 99aa0e18e1eadefad25de5c8aa8930f7a3488206284fb58403df1afc9c4c2543
- this leaf
- 7751dc53aafc09f02d7ed01f578dd888af0a7430935f72cc97858eaa07489bb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eHJJSZ6GWTf55ZBaPDwhEhaRkDTTk9+ecyAHwTYVoOBi/VUYSRi+DrNBd4bCpwXeMsMALkNelYxSeRbvzmK8AA==