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
- 5da071a513881718f3acac779bdc8a4f935a4c50807ccab8a75d1bc35bdb4070
- request
- 57df675bae9eb3ce4071ed5003544ce2d707b28ba6978e232c49427f1449cea1
- transaction
- d7986a7a1b0d2ecf7ed538f97733174e515d12333b4a93ec4e29f9cf04af1b0bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 716
the chainentry 716
- sealed to the entry before
- 036502082832ef2119ade0c2011d54fabace961f551cb624d8c3c2d0b615d582
- this leaf
- a243dd4c4d1dee2d47b675d071729fb1d4c614d12a3f0b2b8137873f2e0c2810
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +PSgiXyZVWA7uZ6MWYh66nLzsXkGxCwn0/OvTmMe25Hgbuu9OtQ71Wa8HSuWMNIj82ZBpgspIdGs81S5LcKZAQ==