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
- 3a138edfdf4c12d634a36254724c1db898763ce66d554cce9cbd5578ec04b7df
- request
- 04ed900b30132c75720ef12c7e46c7aab78ca68f0f452f6171fd2b09d4f988ea
- transaction
- 78bfc74d4f690c38469edc4a23caaca941fddcb2bccc96864d3a6182b5b89019computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32826
the chainentry 32826
- sealed to the entry before
- 91d78da9dee9d9fc5bde277e97c0f1ac670dcc78651670d3b79b6442bc0fced5
- this leaf
- 0396d371ea63b0e31d1586f6a9aefb0a079112a9ae3e26ed2c0ae79ccef4fc6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TGppxrFbUlGhlK7sHxTod0Viw28CeBzl7C2XZBa6riToc/3FsfJgXL7Etpq6/8b1XU30Cec9OmQ35roQSbddDQ==