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
- 228a643d729c26b10137a76a510a645f859cfe060f98ca35ba8ab05c0eafe002
- request
- b17f418b0bb1c18efa149f3fe5b4e18b1d2694e291b91b8703016700c3b89472
- transaction
- d87ec6a48580c97b73e50aaa50583cf7696d81dd1c79197e083403cf2349abe2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10805
the chainentry 10805
- sealed to the entry before
- f0221f98b699de2b5dea6610fb7b2770f5e5995e3a03da2e5862d5225d926b85
- this leaf
- b50c356f4ccac7902ac7370d06de38316f3671ccbf7b38d650d5a777a84a303b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ryb2S8RGkIqbdjIJoQ6OnQtXRx/F0UnKgEJilPTAIq6AzpMRpfFLliyAs4ysSrztg5P6BcT+AoaNEUHj1O/2Bg==