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
- 9c1a62071e4a766b430f0531f5f24682542af264ed5472109e7fe1c23fb51542
- request
- d090aa3004367c71888da2736540feb3c8ac074639cfa080165ed810afbe8500
- transaction
- a5f774d341c3d196cbdfbdcfef1ca7cc89ebac0a88f4c9a85b30d2f51df63418computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16525
the chainentry 16525
- sealed to the entry before
- 2a916ff024b2f17223b650e7128e30fbdea2dba6dc6bccbb099765db6b7b1af8
- this leaf
- 334dd7928b1b5ef29a82fff7e4c27c9ed864966e03273250e8cf7f6bcbd294bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w+Q/ajpKQPk2rPZ4mQdmGJMuKWp7uvLSQybe7Cz0ib/Eos4Nbcw3kzIPgGaue33NZTxhSogLIZl3I7+k4/cQDA==