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
- def9681450513b02f2b006c7dee79233a232e0011f7555c6dcc785584fe4b331
- request
- 6c3476a5c96ec8a323384b1a76ff4450cead648bc235cfb211d8f586fff6ff3f
- transaction
- 95e666c63b0af1ea4a6414d6ef8c944fae872af4cb1e918ebfea075424a83dbecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68053
the chainentry 68053
- sealed to the entry before
- 61175df5b5b1721d49f7eb227db516a79e548e003735e77cc8ea9d579a2deac6
- this leaf
- faac3ea596ed8e7ec6627bc4d7fcdea32dc7e7b3e2c7affb6d2b26aef21e1a58
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TN8KeMgD71z2oU2PnxM8is4hs+Ew/v9na5cjx5aU5u9ZsE8bjNxl1LAIsoflz+pkqFjI5PrCyWXM1x/V7MyJAQ==