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
- 68e165cc1154e7dcc87891e25b619d32a28fc51a89108e716095b3be5dc3e56e
- request
- d642a81d52faec02a1ab2f725ca9b265ad162d5b6e84832c7cda28aa6be69003
- transaction
- 9020c3f6d1ad1ba2d1840adddab6579deec2b590f0e258dc7c81d6d666289ecbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 211
the chainentry 211
- sealed to the entry before
- 181e3e9854ef5252412cdbdb3be119d200a0fc7a51ca61bbaf30df53146b350f
- this leaf
- 6049cbb672c9a44738cc6929bf308ca944b8f5233f8679e6e3e6085a6b7098a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x0Z8XVaN90ZLbhX0tz1VTWVbMubAHEHipxJH3qX6AHIk3q7GcIfHlQ9/juIWtc5NdsIWbR0C11XfdAOZjdV9Cg==