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
- 75ce66f6d9773ca6f22e93fd605cbb7d1464404fa4169aa6cf95642a8a64db14
- request
- d72842243b7d26dbd4ea580bc773d4c2899eab9ea6c9638e02a4bb762a159df8
- transaction
- b6e94379aad2349954b28688d61d5454bc6596d13af9171e764f9301b523adb0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41032
the chainentry 41032
- sealed to the entry before
- 5928ca822727e3466f6d055b7ee1fd767cd13a6aeaf52f63fe2f9601ca8cecdf
- this leaf
- db02aca497ddafdd5809a0b8b7719fdfd73568c1dab938e390e1dbc316a965ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- acKq44dTpwq5UJEMlAp5eVqyqZqsLa8erJWVjJzMaYo3KDSdY1UHnuV5ZLx5R+NTZ13ZVXc/AtFy4odgKfy5CA==