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
- f3f9ff878764a40929cfe10b4857452f30f0b7f036e2ad5a5804a5c560d2cc24
- request
- 97595b2846b6dc660bc24c0eaa2bc1524fb7757c27b855c61ad4681d765bfa32
- transaction
- 53921f4fe1f729e30b6b6a71ab09b97ad51cf7403b0553defeeb2e51ae69ff90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43983
the chainentry 43983
- sealed to the entry before
- 4a1a27a1077a9898ba193c82cfcb2665b9eae1a708a24d43b9636313b8b80f3c
- this leaf
- 0dec90ad2e069fcfff54ab655db1d2c373e96ee7cb81ec09f1ab7528c1cce865
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hiLnzG65JAnSBVaGQp1OCGP9ai2YFZB17rBbQ8WQ1oFM7eLtTIcGQ5A4hzyqVUtDN5lxlxWowLpPSEU/4oHaAA==