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
- 9a3e925eb911d38e835c4d16fc521092fa2a9e2356476a16e4666e483825f3a0
- request
- 74992a1f83f9948d250c28b78e4377e0c55950bfe6205d138d32b605b30c3627
- transaction
- 16806d0806fbd6a1d181359594ddefbd54f732609b6a3a184cd0502a1b47a65bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28529
the chainentry 28529
- sealed to the entry before
- 6cec44b66e56c6302e59c51bb407d68409f9176825b4edbcb59569ff59185f37
- this leaf
- 09ef6956e81d829d630491cd396729ad16a5b9e828e01965ec2b2d3cb39982df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4uLEdHumLn4RvJ9QVDF9U0ZlZyPxIEBInndLqezAYVpLnQ63XWjiwLt/rsF6b1AMGZi54soi1F4nHBqoHz0dCg==