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
- 5afa04988e6fe34462c197204e7863775cb1d48bfc13e219911209b02ed4424f
- request
- 3c62ce00250bf9bca363cc950f143b79c5967e50577a300372c6bdfa28d9c95d
- transaction
- a96a56d3f70475d119f0022575585942c8f6586489b310a25d2bccd301e7dea8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48763
the chainentry 48763
- sealed to the entry before
- d96d077bf561780bed1ff8a4b9c4bf304753c5749630f0e43aedfbc5ea6a0312
- this leaf
- f7a9b48bd25c98185251cfb370c44811a71c7af183bf13f9dfc57fdeb46b9147
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eN/vVckHkVC9wOjUCI9B8OYyb2jaE5OdKKeGwYmvAltbklthb28vySqvalFOqLbSTdp8nWkCAceBIstORS+UCQ==