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
- e937247e42ff3bddda94fccc64e12cea75c5a2a566ac5fb218d81ba089b11cae
- request
- 3a9d9bf77db4db4f9ae55b8866ab49420dbe1cb94c25bc512cd989f1d27a7729
- transaction
- 0d4e20b5b8fdb77fa26f4943a108505fac00070e2e6e43ae535e11ffc327cf5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49151
the chainentry 49151
- sealed to the entry before
- e5e888be15e626a219a8ce2d841d7efefa908026b4542dfa4b51046803b7e40d
- this leaf
- ee1336f7cb3067d65a9a45a77be3c5259dc54ccbe8b393ea8dc8ea570f775f1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RhEY4vIMoOou0EKpZ1RfcoTEG2jmKbXAxfAQSG3n1WPXgEs7bbvgxFV7Heid2jm5p+IsIfwAfi+6oip9z3qcDQ==