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
- 8edbee6ebe340276dcb699b097320078cdfb5da04dfb302f0561f6b0320f8e04
- request
- 6a2bbc5fa36446836a3ae85df805550aae7886a8835e7ea4c9635c26eeca5938
- transaction
- 944688c73ef12a6a8363eed1ac4a51e1f2cd83d4a6043e3c61b5451c8b310e6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42280
the chainentry 42280
- sealed to the entry before
- 86fa7fea3ea2a240f8d17b0b0ae40a9fc23fa04a093b1c59eac773fda24d61a5
- this leaf
- ceef029bf13696fffe2fddb5ac184bbb17e2c2a2b99d0838a4de9998dab9f4a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4g1Jzhcfxtfmqncuh1EEJig6ZOSBfjCzeEOWRJo4qP2NsgM4wyX0L70PLhvRcTRxUvvry/sm3v7sxZt6BFopCg==