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
- 8ada70b498fc43268bc62392d580676d0aad3bd159c5cdec8a86e33025fe20b4
- request
- 81d672ae26b4d384ca3003c75fb7589a91837f2008ae8fbe3f4fd6bd24fd5ce2
- transaction
- 5bb4464b88d112917185c1550cc5606331a540760b96594cd0c7a2652ccc262ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61398
the chainentry 61398
- sealed to the entry before
- f9d0344aa4f6b7fff671e338130c05c70c8983b50df4e29c57615b9a0e48cf62
- this leaf
- 39656e8c607455a2a047126a56fb729339af4ec25d1921441509fe56299e817e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ySTESR8ftUUM67Lgzdwgn81uGuJoHe3GZZjHpqnFJZC2hrdWZ9uX0oBJfwOuilMKhisRa4rDKJMx2zlejtCYAw==