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
- 5be0b903c6b8abb2e244fcfec86784eeb31c2d1a721bc81174e5054d7c0ef34c
- request
- 8ec3a1841512469486d7267490ad06d1b35969c81ae04eb0262b57f430cef6f3
- transaction
- 3c0e762a4771f9ed0d4649e12695d95b75a144af118231901e440f46f8f30729computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53036
the chainentry 53036
- sealed to the entry before
- ae369adeb23efabfab1a92232deee9e92716f6382041e5135f474c6d5bb61bdd
- this leaf
- f417be786da7646bc415da30e8c067e298ee0919760a7ab4c7e71172b8b6c596
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GEXhELHWJLS7srJEaC3IJ1aH9/bpl7GoSHEzkv/UJp91PEjXZUio66/O5JbJOQ2UkzjWe0oPV7oewqVA77ZqCg==