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
- d99b5ccf44cad99252890d4ddc73ae05c92295a499d15eba424dffb2ab3e46e1
- request
- 472420fe4f6f26733eb40abfa6c75164cb7663029fc9a41a1287c3449dd9b2e8
- transaction
- 97342be834d3e36f4a427d72ad446ab2272ca07a3ff5695f6dea1768e7d5dbfbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70610
the chainentry 70610
- sealed to the entry before
- 9d608ee5e71e96a6e1e3b510fbe24c195ee0a1fc2d27350ea136ff320429d54c
- this leaf
- 4155531a332e2edd29fa572181926c3619c0443b8ecaca1798d57f6e8eb3b2de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 89uULhFi4IRZhehbIsIpMkJfORiS8jVc4qN4pb/i/j7BPdwOYh30Ej2YkkE/f77M01uyXHLcbhqIdR4svEWjDA==