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
- eef5b00e43221a745fe2cfb93e2f9d061c1f3e7f4657609eaa806679b493b5cb
- request
- 626b2464546bd79bae7a05474e6f6340b002fe4df71d18c3e806b15df9710998
- transaction
- 17cd176296439952f8ebcd5d7064ca90c74c5875690775ae86d16a2cb081e8dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18689
the chainentry 18689
- sealed to the entry before
- 3a061eebc14e7b485ad33cd49cc0b1b3778c272eb8fecfe7eac8ec2b3c568847
- this leaf
- d6493e7fafdf3b874840e809000171fcde96fad67d0b28481723dcfaf70496c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N+TyL/imH8IjnWG5FxyuM+W4N+VRN6OBk52e2ErF+MWBYBxbxfklqa5SKT0V20pg94yC1wW+M7EvN7GnQ18HAA==