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
- c0e9a6465283de0f4a07492d667949c464f3e601494b564085f74be4ce466b71
- request
- 7b4e104e1c0097a4d5ca3e254b4580bb450ea20a8dd06e42c302bf7c6b4e39cf
- transaction
- 30b34acda8bc3fbc818c8bce914163d2b00d149d374d37cb6b6f846579f86469computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30902
the chainentry 30902
- sealed to the entry before
- 0c773dc4daa11fae80d78e160367e18411909fc55e4830dc835d879a6932f09f
- this leaf
- 586daff6594d465d6de4ff21eb3d415d74b51c7e6b83c277e89c42421f91b4f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g69Ctzbz8smmEsQ0v9LXocEhLD/QUJcieA7Ew0+UMRsbTPuuqr75c1rVIATXjiC5O/x9WScaWm++oWXlFPvXBA==