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
- cfa4190e417b34c56b087c557cf146ef05ab31fb0947f9841725461847b51182
- request
- 4ea85fef8e4850b1cd60736661f00216a1ab56a7b40cb415edc7e993a105bb51
- transaction
- 5599d3b1b317103704a5990a67db610c8a438f1a22f96d3508a98b1895f7dca7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39146
the chainentry 39146
- sealed to the entry before
- 8d6d7bdb511f701b41dadcde82a573e31bd454857cc9d3d475a5c1e7377c1cab
- this leaf
- 7ceeb8b2c04c1eb135f61118ba24daf0d20304e15cd6428c479575f228aa8778
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IMGV3vL71jnDlmRpMjIbr+FOoyt3fLMDIsHlINpWaMDXt+hcqOWsjAYRhy6zGyItK+NDTxTG83mIYVjIS3IxCQ==