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
- f5a5fa4b794baa33a0f53128afb910dadf7f5f12fe7ea03999fdb01039d2af28
- request
- d8f767044a9a24e5e7f2bd0a1cdd4c39dd3721d27bb0805c044df90e9a7ba3fe
- transaction
- c14c4acfe783cc51393766f7231cf191bfbc1f69af009f21b11a66620d25cadacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39755
the chainentry 39755
- sealed to the entry before
- 083d0893ceb94ee738285292048e29e9d8b12f1c90e465b367e587d5c9f30fc9
- this leaf
- a67646a385d62436563149aa6db4eb6d7fdca1d87fc716236d4c70221dc655f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W+qGfBynpeHgJX1ndBjRT4AIeaAiW3aGLB+apy1Y3hFOQCwdjjOHT7ZRBZtyBlzstjZsyYr2+lNDdu3qJ1KhAA==