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
- 9b60dcec784ed52465d57cd2333e489dac819b11bcdd42598005a79e5e4d010b
- request
- 38a6d3d53148b1945c06c4a3521cf853028a85b28897db7dc3e1b4caad0bd6a5
- transaction
- 7cf95650b440ff99c729bd2c5405e75ff2ec6b43f88c477551c25b4bd6afe21dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52342
the chainentry 52342
- sealed to the entry before
- 5f6beac712173cde32d76920baa777bece09648f2c538884f0f759a6dd5d9c20
- this leaf
- 750034f327481127875411ddf75342d1501e4b3329a2d8dfc9897c7acc86bb4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f9XS5K67nbufpj5GxIPHaOqpC3d0QKaMiN9P6OyHG8sL1i+V0mG3owkucnN93Qz4gQJF+0hf9lMoWhisTY8xAA==