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
- 6a132540519bc24a663e735ffb70ef712bd5bf5d493b7f8638e18c9efb219f86
- request
- 0146bb9afb4ddfb0da3ce6a91e3ac1ea5bc455eaee0008cb1b4f0579a2916a5d
- transaction
- 61ae4df8e38f5a4e3ca9c02dce1869f5a775845fab62f82eec0730cd29fa56f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50605
the chainentry 50605
- sealed to the entry before
- 8b9ecbd7de1b6443acd831672a85d4397002db7d1eb726e4762e95d7d1e44eac
- this leaf
- 64d7a4a47f0e11450c8f9cbca6aa2246c0bc2f7b4e0b218f6614304f3c9637b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MOqCR7qTAXhF4lt9QM4rPb6I0pvWkPMXQwXMf3nfsRQYhwqB3CwQBH8IEDrk7G4W2IAeHNURFtQsJ8hG9HnBCA==