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
- fa5f80895422853bb6271c5cf7b2bd7531c60ddab75b7f270e1252a423978275
- request
- 73552f9d9a26451c87c39673aa11e1a2c15ce47ff084d5af63fb4f5ab4e2e13c
- transaction
- 5d5dc981f147880e720417068533de91159ed668475349f96a596d003af1000ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47874
the chainentry 47874
- sealed to the entry before
- 3cd1cba3132ea1aaa43826470e9b0afc148c88ee0db802fdc61a6c15bcaad66b
- this leaf
- 3402c2448edf789748bdc7c2932fc7d5e68abc95aa4a0a6764b422b383aff6ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gF/3AsXewvg7oS43WVHh1qqYIGPA/4BwCis2RwfAykezaX3fBSzQxt42fY9CiAL/CCE8SZ+YX8kjT3fKbT9yAA==