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
- 030db881c67ce9d16a438d28bc84cf6488ff7148ea3def7b9cc001aa63c2328f
- request
- 6157fa30834dfa0ded2d34e44c053d562223f2aabacd32be43a1de0628b04a23
- transaction
- ce42b0e1c12408711c1e2137f40a7e1b3db99f84f8c6bf31dcc8999b1a3828aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73454
the chainentry 73454
- sealed to the entry before
- 8c0396168326b52dfd35c88cc09da77ade24afe312175a8ab03974c7b30375ff
- this leaf
- c90bdb1997b251add05f537b7e5e4bbb2651d2695de10896be6d4ab5b07a5401
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aRaUJsNXI9f1amj79txlfWVuCDhTURlWxTSkWX3rI9tmKFIXaPyCljiUW+pr+a+nnhULrhTnjT94KpVwGUthDg==