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
- dd5d40834655e26ba66609253ca6e744a8883f094d54bd2e9585a76e72731aab
- request
- edb285e3a7664e0b3b43d0c90a2e7c8b73e1f7327c266db21bb51bc80c5469a0
- transaction
- 027f968bc8cae6e1a595021b5f381387822c17b2785ed14b9126a603469353b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42505
the chainentry 42505
- sealed to the entry before
- 9031a3a96b2696d12054c71b89a400eb5bc71aeb443f7b8096701156af455652
- this leaf
- 49bd1d6a27fc9efa894fe071a6573369d0d80cced42d571dfedcd35111a1217a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LXZsXnh/wJ15nzCSmNw4xCu45+hhH5xxTr7vMkoNy6RI4bUo5RtNoRpxMuEkGEhQYUyP4i9Jl9oTYsLaH01nAA==