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
- 380f3f7c23985d46c103359c1cd4f6e28ba7e89c4219655de4c9d5190705d166
- request
- 231c88d9663f144685cce2a2db6eec8abe2cd64e884da1d8a804d7ec0f272bda
- transaction
- e0643f945cb5858a9033cb9f43ced17f62127b24244393f4312e5ebd8f63f2d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10547
the chainentry 10547
- sealed to the entry before
- cb0b3506f2daf0798db1b4c81fe6817c104daf3e7005088b82b2ee564c969ca1
- this leaf
- c76461030cd8896e6135c315058d9478192c1d5a86c75443697b2f92a1a5420b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eBRgHM0u7x3ixm8voFfl5XpuTd/9UpN5tz7nbmt1K6HqTC2LAdRR1TGbuj7HqxSNWS56R/mvLmxj82VhC0lFDA==