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
- ce85721be867f8b128e476d5353eb5a39cbe96a37586441d81f623554e0120b3
- request
- 814033a62f64fc531aab8e99548ce44d268a776dbc6872cbcf7c2bcc7e569daf
- transaction
- d19691ad0cb7077f18a42c71fa3404fd879097c3788c99f9d67cb6cbf7ba5797computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58183
the chainentry 58183
- sealed to the entry before
- a590588e79d1b512460e87529be346912b333e51e2300e03479a9f0c70b0dc7c
- this leaf
- 1feb89177f7c5a1f4297ab84d1f84dffb9a643ef957575d069cf9048e0a33895
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /wwW/m/bZaMBY62VnAjgNDfKvF1SDmyPwE9q7fkBLPSTARgxJ6/lsZUUGNNvkAopBsBuJF3xdoSREgHBaKBfAg==