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
- 6fa1ed829a216ede6abcf144d33b2235a606caa0602c3aae11b15432adbbc2ba
- request
- 03fa9ff95dc5d5868869977c6e59a700e2c5ce211cbcde5bf6225255b2821375
- transaction
- 378e8e14e34b9917cadb23b3a1ce0bb2ea5308b04c6fafcc86440ae01f7bf733computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34030
the chainentry 34030
- sealed to the entry before
- 5fd98a400d9a75ed3a75fd0c0a024912d6dea48efa1ca235516c05f59e5d74ea
- this leaf
- ed5582f5d51b2604a4f55035c9bb804d7ea00bde696dcc00b52b499e465ecf01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SRLBafOzJchRuqxFlWKKLC8oz8sCIlMliBu8TuTU8GmIcC15tIawx0/IrATUmRn/rj5KnMtV77CPArQgz4OgCg==