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
- 2d7333c3f3d091c783b7867074f61b6546beb7c352d96e21d1f6830fd94222d0
- request
- 2a5c61e3a837770f27a67c04d27349454d773cda995005588ac35015293cf841
- transaction
- 26fd575d8c8538da60a8a63d1cc98489cb08d0f653b7675db4471bc9d1c4dd7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56344
the chainentry 56344
- sealed to the entry before
- 0439f55eaeac349b3b8e6fb3f41cbd693a7ea44bcb6ed21d6dac6f809b9b8926
- this leaf
- e7d7e896f5fdc5568c1a63db940eeaf327ddc79f4c2be16910d77ba0bc87eeb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lg94RdZVzPv16ZkoHegzFGfu+8mROKAdmjppF5L2Wy5xRgCQISafeckHwe2G9oXZks/5irEqhrol24yLYCluBw==