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
- 50047308727cfb7c073081d7ea9e6c8a74505491b7cb7202a901fea916b33b4e
- request
- f778b5691f9db6b2d53a08c71f5777aca1ac27cc832b3fa3d11246a8c2027546
- transaction
- 42921622a154c1532bb6bab64e016a4b78e74f8d03426c76c7178828d3641661computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70450
the chainentry 70450
- sealed to the entry before
- 9b7743a029646ef0676a8efc49bd8459dec6653ba0741eba6bf3b603518c4227
- this leaf
- d608be8c4de0e70be8de1b4c599306fa09ed2e9841476f4668243c96f9514605
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NNsAqFyiSgPY1aOi0bng+SJ0AjFvzpergbauyHhGTzkL0rzjhyoJyqfiIP6OiTLFhiD3l4sZOUIUbMg2B6zlAQ==