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
- 683adaab209aebd4e0dedd596dad2f3a61154ba76e711424eed4f59ab4589176
- request
- f0ea3c8535a40b52e4b061c60bab29b213f063594397ae23e70c95aac05cca65
- transaction
- 498853e999dd660b4cfa5e3ef9adeb96be61e00ca8f952e5d693bd4814342fb2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61721
the chainentry 61721
- sealed to the entry before
- d73da504b14a6817e7d2819215ef4127e7c6d77549702045756dc72a6d0412a3
- this leaf
- 5cf7cbe5729141b34d6a2039923b79806533adcf43d72337964f77436ae15bfd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YDWtkoSGefQkx7XnOzjkRy4arVSbxadkcICeDNuDB1wjgE9VGACrIaP3hwqJ+fNo2SQmr6AYNMgh1uvjOBA5DA==