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
- cf0cf3b1bc7a2ef23ae44bfd6350137a6e3182b66ed79d382bed039689b0713f
- request
- cc9e765a3ad423291964717de19777f3ca482b87648180ab04d323ad1ff5cb59
- transaction
- cf0a1183cb35d2448036f177748df56e170ad88756bf55588a3f84de28d3b339computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15809
the chainentry 15809
- sealed to the entry before
- b99b34f515c2b4082d2709854dd2d5afd2b26f6a60073a8cc833659a241011ba
- this leaf
- f5dce20986952ac4b119176b7fcb97679cda1538fbf1b470f67fe8b85b14dc1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ClTXYniLslYTdVp31nzAo8+KWTd4RVyiMEk+lTaSahQ+evLWEemgql11j9kPgsQN8siewtNIUKwRyI9LrwhEBQ==