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
- 2e0a8bc2d323a1f79fb4e3416080f7918f9deed29143ee9c459b18fb0f23c384
- request
- 7920fd20e1a28ece44d5d5aefc93d904b37d1778969c0ecff27bd11cf95bf344
- transaction
- b58cf52f2c44d601ea64db8dff812cf9452d41c91bdfd1ea48707222d6be1350computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9683
the chainentry 9683
- sealed to the entry before
- cd2629ad3d38032c58f554b8b6413327a0b95ec1bde6a8738c7deb959fec2a3b
- this leaf
- 512d74cbcb3f2b946142166ffc3f2125fa01fbd6c6dbe7c49a978f672d8c53b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KFeP85q73pEXfGSACSU19/jAgqbpfkGPLbVD1TIf8PAcwoKM8nWW2rM3Vf3xgGuwb5yAe7IbHqO/Z1lRFxkCDg==