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
- 5b84b0568bd2f75167186cab31505cbdd0d1f697b332e0eaca6214db0723cc7b
- request
- 2c6f4d89a2fa5d37436ee66cd6aed2c76516a96be1d6991494a8321174af8259
- transaction
- 96fd8fe26105057dba2683607f824cbfe17394b3e5fc78e5a15793dcc29d4470computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69107
the chainentry 69107
- sealed to the entry before
- 7ab4107c6d9b127e30936404243e13a615224547201f88c9615af03f2166a5ac
- this leaf
- 698550874c2191c4bd9468632a3d71347822389fcb1badb877eaeef9e20ec7e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QUK8SOEp7978yZnyf+e4T3O+odyC7AOTJAjPv/fsyAL3eAWSKF4CV5hMx79FNSy+KljYM9iQjfX5oWuwJA/4AQ==