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
- 869d627e3a81cc91db5f6901a7e8f219f14296bdcf0c28a1792e5180705effda
- request
- 54d475dba4b4759607daa50f42a754ca8c32d9335ab803deb18b0efd41b17ee1
- transaction
- e4a2659649604af0348237e87b7a6a4f7cf236f660eb4ff0933139220cf3f927computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74533
the chainentry 74533
- sealed to the entry before
- 493936ce10570be55b243ae6532e87483568dabda60b6dd0896411df2a00fb6b
- this leaf
- a3b1f08b6413e71a329b0dd0041238d3b89435e498854c7a79c0f93ddf9ab6f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Gi/Y00yIlG1EVC9UtzYQ+7cvkBZPcCxmqEVF03iT2sFakKNIGcb2oH14EAgVCb3iq1AzzHV1xJFzxcJTZPcCQ==