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
- 893b9f6b59609eb6e45c5bc55a9143bb8d4c9c85d17cce8767eaca55176d8ab8
- request
- b250b86589fb62c49ee1d3bb2106482967dff69a2ddc42119ba7193e26372a32
- transaction
- 959eccf210fa91b1b94155c413227348d5f466834d76702db1a8f52438f3a2f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 151
the chainentry 151
- sealed to the entry before
- 01308dcb086c5fa7797b1c88a1cd9163c36985279090274053f8ac662570ae3f
- this leaf
- 28bf79e5af88cb72d3ce773b9e0cf818af520dbfaad0712aea73039d4658e42a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +605nPZ2AoGDdomBET/gmz0j7qgM3IV2CMuf/zSxpzTzQa5xPo2frPLVI63k3vXNTEQ7TlaPUMCrhYRGpq7SBQ==