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
- 9c7c4f28b4bb9516c88da6d89b116137075ff0f5208657a9a327d68c441d4414
- request
- 49214246ecacb128cabd37bccb3f3f5528e4caf07c4391b7170b256ac53045f5
- transaction
- 377191c8aacf50892806e18e87a6242da3e530b9c874130793b9a8faef59d15ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69301
the chainentry 69301
- sealed to the entry before
- c2ab5a27f50abd85e3fc5fd5ef76ec79cd0ea962d36e6fc4bae0acf2295e92dd
- this leaf
- c482c42ac014ef8cf137d865d07fd151f93c855971e33e6654fa19996f2666fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6Wfc8cJzgIs2uZ9QSDiOLUDwwHTnk4ptczhM2MbUg04uj0CFKu7v030Fd7+8fgVdlT4DCgKQhbhh//G03WkCAA==