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
- a85202ee05fe505ae6ac900c0774b923cfc1009003599ee546b3b78e7ec069fe
- request
- 8b54cb3eb7b81ea041773302e210d51910c67955636d46867bd7bf02bac1193f
- transaction
- 653c6a0b66b73297695e830ad5bdc5a7f9cabb94b1bf3f4edc8f5d0400ec090fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58498
the chainentry 58498
- sealed to the entry before
- b8626bff2c4e51a563acd2f17cda8c65518c962ef8e3b3a116543750f36c5424
- this leaf
- 3a5cb7c7c49257335338f992df63786d7c0dcd95248ae30f15bc3564eea08cf2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iGpw0AlY+sj0L0IfKtVPp32ZjJozNbgNs4RRz1sPjakzGJL18g0/EUUD5RE9dDjMiUQlZIYLZ3dFz5N+xyGoAA==