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
- 6cac2c1d14b14037ddec9866a34591ec9a3fea64b1f5a9e8194ef454ec401117
- request
- a287921e1d562c5f965a17f5084292f0e50a6e8f5c0c6939ab3d59dcc2dfac95
- transaction
- 94f3cbd403a2acba5c5b7a1626792a2ee2756f68e0f9ae0c5dd86bee7c983307computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12406
the chainentry 12406
- sealed to the entry before
- 79da0cc595913913f3a18f4aec30627593ccb49df793b643b8667c7e6d455c87
- this leaf
- 3c191c46bc2347fdea3cbafa8f65b0bb1d06985700ef135f7dfe18cb15dae038
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LEgi0DW29gt2povrkj4s1BdTA915dJ8SlhTDuaMEWBJGUegiUcss4rksQjtrapSvnzlv5KK0NJDNf3HIrLV+DQ==