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
- 648679fb61782514650fcece6486b0f3cd9b571d8e169e522d95b6a28f14d454
- request
- 7eacc95539c0697c592a252e77daa8b11e72ac01f38544b58a317bb3f1278e8f
- transaction
- a4e1c77a1daea482318326ca7da84107f1a58a727aa6ba162c3f147bf4a00d9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63925
the chainentry 63925
- sealed to the entry before
- 57451ec3d998e5940ec94ccc5264785c070d3759a22548b47340b875187d8d5f
- this leaf
- 4925d9aa2d4e8b13593513778fe50758d141a347e670da9fdc47f0888db3b511
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NAOn6UzXQ+dLLYJjRcAqdecHb7v9LID1+xfiy3NIzjLboc8bH6tt1OfDe0yNni2AMZpW5cvwf/ZbyrBUjwhWCA==