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
- 9ba713f1dc9e54a83dac6fea485eb09ea2caeb615a3a0ad6a81cf1a141f0a74a
- request
- b3850baa41be560f18d72b35483b23e60a90b4f1e091cbb1847b4fbbc12555de
- transaction
- d4cdaa2e8e5ddd9f42f24b5f696545f9fe61385a753bb9dcb36a9df925dcb06fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21843
the chainentry 21843
- sealed to the entry before
- e5392ee494d3c02249ef10d621a6111171e90521bea214d15815a3f5b3e5bc26
- this leaf
- 22760dfd0823837fdad7bc6f3c7cf0a6a405075c690ec474ffabb4fe8616069d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UmXBhbxKj+Tjkl7XvhAxkuDhalicJamxbP8HdA2BuyqFARplhsihYqWWA5sBLp3Htu0hPCR6JO8paZqPmsscAw==