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
- d5c07e69c0b0b52aefcab3d24e30048f43bb72a63656f159536b59a7cc5d6f10
- request
- 1e16b95db800dd8c7d3da24e3ac394ffe829801673e9e687d1352c9b3ae926de
- transaction
- 445d5382825beb7c88f138f022e0f2f1e38deff0322585af5f6a91408ad7fab2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57083
the chainentry 57083
- sealed to the entry before
- 2787361da7919d4a9727c0540dcb5fddd1b11b485827bf412a5f7c1ae1fc25a3
- this leaf
- 84dcf4b832bc978e55278e3ce86797ee81b83f4aa38cf2c198c3ee86fb0b42da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0LgeEPPL0zdTprTbsYuraIzNzQhNnR6yH/anzwOL26+Eh3jmLfq7llnXKXtO5qvQi5PmiGEiZdcbRmKoe8pcCA==