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
- 6b9f9c461a7f45f3dd85510d0a645fe3f25cd24d9433648273bef3c3c762a5cf
- request
- d90d6c810842571a69c0c3b29dd609a87d3fcac3f4817fae359d80c86f7b0774
- transaction
- 014aa5ab63019118b8d764ff8ed4959a6f6750bd8593a4cb99da66050e7521ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70138
the chainentry 70138
- sealed to the entry before
- ef0836aff171995b2985b591cf46d8f786a3c5f7777323ebf3380f29d711822b
- this leaf
- b1362c180c4ad6f4a418b10b4fc767fbd9a54d522619230c4c2c943b1e199f35
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P1DePPfrRaBzeOfLwJH27j1hD1TsO4Jxlu/Ujkf/3YfqepgIK/iwF1bOXhq5q24w0tULMO0ly1Ip8HDdC9s5Dw==