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
- eb5a3e97504e070dceba35132eb519135b0ac5c66a83eeba4824bfe67b7b2f4a
- request
- 1f0e55da2eb7b953bf134e469240626150b020e2970a1d07156ed3644f89ecaf
- transaction
- dbb216efd15cbb7be079ad75c38aec04646b0d4a65fe7f6823dad5f99ef0420ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2230
the chainentry 2230
- sealed to the entry before
- d6c5b4a0951c59bce2e68135e39da4849501bc9711abecbf1cde850460d326e1
- this leaf
- e9ea99f22d728bd55f24f772ff1a8d817c70f2527c3c5701768f8befc2076e13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iYcwgK6n8vVO/mX18xLA0cKNrxhH2/rifo/4owIDlaL31BrvskF2AUBnp27Bp/xvil+95exqpJt4y4QMhtWaAg==