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
- c0017840bbabc3fd3257eacb987551a7a64d2287d08d3b0b4e8adb5acc1b36bb
- request
- 4c6c65fc1d967d7acb0068c538f567f8b9ab55b2275ac747f7882724feab0e82
- transaction
- 173cf7351e9fe32469525eb43c725c10c158e0cf32880e3dd2c71088cc87d213computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28629
the chainentry 28629
- sealed to the entry before
- 3d528ac14648077590db8ec3a3a744d640db1b08a70e0b9b7df84dd8b67c8fc1
- this leaf
- 21168af735e60622fbe48f329e6a24c4b957088f9cbc4d5c6e60aa3b183c37aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xy+wcqI5wm3VeMwrUKJmAZ2dkORkgx5nDq3m4ujb7werIzHYS0qjfq2iw3W7FKvmosieRyvZGCR0gVZrXPbbBQ==