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
- bac836386145d90727665a3461ff19a699cb96c034d70e4cb1cab17d23a4054f
- request
- 05ad71ce34c3ddf9c05116cb2ac517300a76692435459fb0b70cc60126deba2b
- transaction
- 28e0bf4373c2771760c2e93791d7a889bd5571c6b19a88c1d5397ca148ac6358computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4670
the chainentry 4670
- sealed to the entry before
- 4d9c3edc16408ce984eb1fa93b9b0e46084920111555fb86c05c7f6b71a19f94
- this leaf
- 855fc26c0ecf1c12c628b454c2bf662ff70a1f5f43db48fcc419038a6b0bed7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZQJrJgekLBIryouzVXzy6LLFqRvD8lnpMLNGs3Rs9z/f+KQHQyvSPcnUktrb0w0ECu/9Of++xdh75A77oD4sBw==