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
- 85c78bbcf68c154a02635dfea70d06aa0ba37cea03c2c65ff344c9ef1902c806
- request
- 11d3872d7bc08ee9d14da33ae973338dde22f8a622a5ae7218896d6ca080b6dc
- transaction
- 9f0751398f69ed3b944dde26bbbc6b4335817afe7851ffcbb6698f04a46e939acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21643
the chainentry 21643
- sealed to the entry before
- 3a75b899dfb42db1f4dc52c815a8e294649dce78d20d6ef72a98cbeb8e675f05
- this leaf
- b842ed0cb0ad296ec7ab441a2555bde1364ffd04854e489cbdc33375b6bbbe9a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n0c1pYEYqGXaSTezwpqvo3QpvHh135If97jqrmKj6oumrvpnQpqgcfx2gS7rwtnYtEHDxSwkQ4U6ve+v3o91AA==