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
- cb065b9f9197830a3db321fe77c05954be175470d9eb87f060149162d5a16261
- request
- f6ed11e9254db06edf1872c44658562b280bfcb1e898ff4068c2e2bec175eeea
- transaction
- 33d5d26157423aeee5bf59ce4cea05018dddd66a7940cd02d60aef180bd4e232computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51522
the chainentry 51522
- sealed to the entry before
- eb4d7af4422ef71531a8f1d658f99d2fbbc79aa643b00e1080ed1a50cfa6b9ac
- this leaf
- e3de006b4a9b24673cd75a38822193501f25ebaf283a089128c9a575e2213971
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y2aS+/JDIDSVS3sLY2gDGTXUHtQUMsqLG/yHUGRSAv6TYik5lt3rvhEVhvc76o2tP3seQcznNwC+B4UTUTR0CA==