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
- a950797eb90ee480b6cd295d8a3050083cb100582920aec53625b625fb8d187f
- request
- ba22ebc0c1c35eb63d7fad3b6d07cd0fecbf9e3ef28c79a3c39ecc0e31410ff8
- transaction
- 54d2b35aac69254992b1b6577ab13e42d7a41239366d1151301fde5e5b454a50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10442
the chainentry 10442
- sealed to the entry before
- c2b96ffa6c60323ada20164cd5ef45e833bc425d8dc6a058814e111d94c2f1b7
- this leaf
- c02a61895934bf8a05b9a9ed79ed4e2e841401457cf9f70f4139b1d96e460696
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yMWFYjweYNDV5DbwYtn4nH6BGyrjqNHDOsKyobwyUr7pvwwk3OYrTk0l2f9ZJaM6okLABLBawD3PU8Uy6MO6DQ==