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
- 9a96d61a6265e8e7686f278bf2091bcb9c111e23b229f8da3f2c9014c4f3574d
- request
- f6f4f44c452abedaec254fdbc64e084394537edd90665f50eb478775ccfa020f
- transaction
- d4c714dc8a1b5086536935b90460788a71ec8ce268d1c7af7a1f24b1ec7e75eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41751
the chainentry 41751
- sealed to the entry before
- 66ced41eeda1007a0513010629b70a10986977920cfeaa88d4d750647c8eab81
- this leaf
- 4f5c6840136cb37f578b7314aa6969849e686b723ad782d64abfadd4ff7c975d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e0CHbAvNMzs9qa1ZyG/05OPh3MKBZm63jLsXZqCV06N2gZ64mFI9nqPXj6lvamv7heEjg2XlOgGvJSptkQtDDA==