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
- f6c3879076cd1c2599897986293269a119b427f90a42bfae47fa5d5d57932dc3
- request
- 9da00bd0d16ad81dc1468ebda926076366fb0b748f7252076e602db93cac5241
- transaction
- 504a50bdfa417da2ddad0e9127eb210b009e0bbca0e39b4554a9a153ccf2c4ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41093
the chainentry 41093
- sealed to the entry before
- e6bdeb55ee57c5f0f964aec23c5734fa0ec70c1859455c48e4d4ee71d729bb71
- this leaf
- fe442e207407ddcfa2b0692c4d4503a8b939a9fc8d5ea132d1d3ff2e7ce59af1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L1AKQzo9pgrjpgDJxfyywdKVmsmj5tG/AJ5QMraDiCv2VL6JHWPxSPcTwUKPbKQN1xWbhv1qWi/rJhiCofXuDg==