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
- 41f41348d8cf4ccb04d79622e0d8b255fa88db4f708396dbab001c74627381a6
- request
- 2fc6a09f5bb5c9a9936dbca68354cdfae6892113579d01ff55083b83a1ad3745
- transaction
- d3e471d1adb77c1db1934284050ab1527f64cca7bf72e6c666e1740dff523ec1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42722
the chainentry 42722
- sealed to the entry before
- 4e528fea5c8e74816cebebac4006711c6b0b84a9d15af24d9930aab9fad13aeb
- this leaf
- b54cba54a62465ea8d4d93c074ef7e407f8e3a2e5e8e77b920bc59d9ec1a72e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 98R1SyLfT/ViM579ET/VM/OHYqQdT4rG/q0F/cuvRqaOIuXtYlGsBhVSrXbXOKfHLzl/PUB+a1vArGohdvTqDA==