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
- 3f194c581dec3ec93cb0f087d8bf20c2a8b5d68114661cc0015286a8d48b53a9
- request
- 0c345e4a0ccae53c9b2f1eed349b2f902026b63c0d41555b6959111ad3b1bd92
- transaction
- 4544df5aab19eeb5743f2bb7e7480dea70dfc07d6682ffa503e84bbe2aa0500ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77402
the chainentry 77402
- sealed to the entry before
- 162be3a1e6be6d98f4c1d03c2a0ae16ccaf9a5265c391783bc974efdd8f7d04a
- this leaf
- 367e7ab0632c77554ab201c891bc7bb1fa22dc23f071ba72e661136a1b4742a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kZQi3EXAc6HzZue1PV3NK0Y916sxMLy9kBxNDuprlHl0LgveeoG+7TEqA9x7PXFPcAcAwrY6VI3Wb/TglhCjBA==