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
- 138a906e3a29b767f98d8be98a238ffedfb0ad5efd9e998d715a753f33aa7dc5
- request
- 262d66ab133e1ba5747f58290ce0704e44bdd1d53843a4139e8781ad6022bc9a
- transaction
- 5aadb030cf55d9fb1c67963ae444f5f340e39c09e016e184fbb7c89a6abfbb43computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7658
the chainentry 7658
- sealed to the entry before
- 27885485300d40ce083ad3944c6f8b20200987240a8756496a5f21d782c0cf9f
- this leaf
- c21155975f9872a3be45dd73bcdc17af7c8a756db800b48d735d406e6debad70
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1EokfDC0RrP5+aBOqWxgeL++SCsmRgHHVLDnWYUDd/HoSSFARrVGgHcG8OCIiE6t0KrOsUSuPwfcwDenYMJzCw==