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
- 07aee5a7f4523135270ad9816b57411c90381d14bcfaf933c6ab668b4943cd9d
- request
- 113c7214eca10981ba2fcafb411d238c23ff555330469f6701d76384acca8ce6
- transaction
- 80bee54f9bfe06fd937716963dcc52ee4e9c3fa00b2c703d4a58ed13374b458dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70279
the chainentry 70279
- sealed to the entry before
- 8df6a304be711cb33c311a3b5b692785dc1ffed4bdd249ae439a9d3f55986c11
- this leaf
- 4e8fa7cf3e45840ea820961adb618ed36903c5083af29d531b4620a780c5d8be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZMEo05w69QbXOFFPQS5qzOHw+RE0xHDRqbwIoIF/edZLuiJP6wBl/+VCD4wGPDMVH7PFRNHfYBRqGZcrz6HDCA==