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
- e830fec6d6b69f8f876ca04f7c471c30dece92a89e2ad33ea14740309053ac49
- request
- d43a275242d6af3f131c1532ad51a8f4f72878b007850e4a5142821d0ab0f1b5
- transaction
- 6988a8321ee236f0d67f7ea4ba462d9b45e754262d5129e67f919b2d6642113ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36001
the chainentry 36001
- sealed to the entry before
- 4d59be41a7a3862176305b3f0bfeb9dbe3b807ec064ef1c0d44f3fdeb2244aed
- this leaf
- f8d42bdeeaae8677a77930924329dd36f1da13af4a7dced674b57d8e5f6b7a16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wykge11ebZ14Eh1eKsyg/ardD9bHDrnA/Xd0qUkLMmSnPqhc/cjG9ZdHSHOLp6ShTSoPu0giBp4nm8f7eD9CDQ==