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
- 9aeca997cd1b71936ca81ea5ffa0e38b456fecf39fef7b060e607aee5818e15e
- request
- 9d23a5df0066a62f67d98a81d8faff87bdee7f357cb4ff4c9307b00c8b154ae3
- transaction
- b3c96c9783a057801406bc8551b8f83a12b19c38af45080ac4f73fdb82720762computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64864
the chainentry 64864
- sealed to the entry before
- f0e1bd894f62cebc9fc9f36c1448f816c9a7238a2fdfec4f77783ee1d723507c
- this leaf
- 5a5b7111c3bd40caac7bfde15afaed3e1c1a2a2758b0704e2f6b7523c7a22214
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iy4Nzwa31GPwu+HN2ivLHqC8WBJ6tn2NFuH+SXfWPCEL62tji9H/HOSEKn2FI3/sDQhN8q4TvgTJ3c8Il5ycCQ==