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
- d41859f41ba5706c265349b63695da2434745c5db7f4e3a84500f7de0b899461
- request
- 2271e53cc1ec671ff1a17401e56106eb20eaa02ee8bdcefeace359321e8f7c1c
- transaction
- 451bee2f801dd47003d042837f91623b4790bed466880f4d6a8046ec3e999e53computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61644
the chainentry 61644
- sealed to the entry before
- 7e698bdd0d2e2aa037effa8bd33be6d9cbd1053114687f2d49b29b04ddd00f27
- this leaf
- c601593608b20250f78b2cec5129a480b3b0d673cffa4bfc569aea47d21fdc32
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EQwSFVSMp5h6trWpqCJgYPSpQ47rvhJJhUwLPLpiSyIIamn3cjo/e76sYUMXUPlrjNd20KaFOAlpdho2Rj0gBg==