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
- 6057aab9fca4d36cb9c55d6dbe5e7da00133414a7bd3db6d5bfe86bc949489f9
- request
- 7775b638df7d7dbc374c00974e385951cb62417bb69271770ffa7e31d3090a45
- transaction
- 9c3fef373a953201fb150114d87d80b86be6c05e77f0453563bff8ea26089200computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30466
the chainentry 30466
- sealed to the entry before
- 760ef842bde1a3bedf214a4f0aeaa7df5e9888571c2135690462cace08bda60d
- this leaf
- 899a4305ea336e8230f01276c3ee91728651ad6ed28d3e11542f6fbdda49a31a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KDpy59GVyeTZObC63XNm5UPLkBkn+rSj6UbN0O8xZFRzO0yRMXBGPXsvNH2QCk30nOSET9+ZRNSvZ4ddEG/kCA==