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
- 8274ab2595ac34187719e3a4ed93a85b7a9fd6682d6024d7f8259383791fc692
- request
- 79ca69dfdfbbbf19e27d2a159283351ef849c1762336fb6d05062a3ba804c8f3
- transaction
- aeb1715eb24bb4431dec30baa07879a4231b804f1437161cc30985fccfa1155dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59182
the chainentry 59182
- sealed to the entry before
- 94e90f233ac97812bba53500c66cdf2c6960cfaf31b4ec26a19dc1350ea2a33a
- this leaf
- 2516ee166c408a3fb782f607bc8efa2c602508693d7010fe4ad255f1f53458eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oiiMdobrvSVllCziBOoXOhjeFraoAUP/MjFPBS7XqA/HsNQ4fL08CfIH1ZxCZQgpL97CXneu9C/bm2OO/hviCQ==