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
- d6b9926daba99cfdb7542fa5a0e1b74a949d51bfa261b55cbb7b97aac388244a
- request
- 9d20206c07f2f8ff7d963a65076cb996aee50624dd2e343a0e28b98186215ddc
- transaction
- 20cb2e1879ba55e7c0ce58169e30572ffdec1208ec33d5ee64a962c1835af6cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34147
the chainentry 34147
- sealed to the entry before
- f4635d8041110ec03f56a11f849ec0880a8a0b236a76e709e29e0e560c3bce1c
- this leaf
- c3fe49629cd86a140a11d240773f429186beaedbe9d69a9f6f26a90f5949cb2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tFQ9VvvSjilryzrqFQT/yw6N/4ETz6krchxEBXL3ANtxoBE1GuE+/tRHBVIviwqnzUoh4WGC3MeCIpTt5GCrCA==