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
- 2692cca38559b9680a5937244dce81166783240182f3d7bf66efeb1186b5d25a
- request
- d468c62baa6a26bc9449e9ac02c88bcaf2c463c2836623c776ce78f90ffc9061
- transaction
- a5f3818317a643eab3ba4c2c4f8bd07f45217f6f96654b0e2a74f5951f4a5db6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1440
the chainentry 1440
- sealed to the entry before
- f6a714bfaef38e0ac207f35aa85256c91c9771af12d0b78cec8a9e77cee0cef5
- this leaf
- 46a30c85b076beb726411934d1ae7c5fad4a2cac13231179378a0045fa92992d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ynAWQHocMP2JH1Seof3dfgECuVs94SLIPjisWR7T116TXLeoiqJzYlvXGu2/fECB7llA7358VUqbewpmJMsTAA==