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
- 3226d79beee28925843e0d769530037e794acabde02f97f22b6ce1e29b50aada
- request
- 0a4470884ea46f1389045d81360d142cf463e69021be5cae4c92f5677d23431f
- transaction
- b84595e6c83fb192122b284181525b9755f06028dfff26253d899f5c9bb9aac3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2560
the chainentry 2560
- sealed to the entry before
- f9db745c96e108074e6a81c2cce162f959819473f7a6505c9cb3a3bfc39ff66b
- this leaf
- d0d1775489afa32aa0c1fbfb59b5954db3c59e5b1205c70415fd713d30c62be8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DE7XZGuzHugaWEj3OWGllgFj4IIxAvEwwdrqWrmfUE6oBiN8GcB9AVirZbzDk/ZGdca8A/mPDDOm3bJSWHjRBQ==