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
- a0e77b53333f54749e99a7df86c31779ddf102b6c7b9612b16521e893b6a8eb2
- request
- abcac2899fcd97da3628dbd080b3da063237af0b60e3db0c1a40e7fea6bef0af
- transaction
- 2015881585b1472e0383551e8fb1da56aa3987aeaa8c4f059299cdbec6501293computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34771
the chainentry 34771
- sealed to the entry before
- f3df9ace71dcb9e40504701d9465d11e537837bccdd053759307ecf0b4e9cbd4
- this leaf
- 301b31b40e7b204a3c4aa8a73150aae21bcb488451b94f4753148588090a229a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vwqJ5sD2LHSDUhdLe84TTFOHwfs+g8Qg2dEwuMPXJFhqIDBGxllagLsmNxevyTrkkfXmzeowTukRPhg4fI9xDg==