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
- 30597545a41dba6cb7f711d3d22008d813c098f3e3bd3d08adb91f3a59397072
- request
- f39a1c90515437252279c1e32e92f67d2b0a6a7ad84c603fff3e78441c87d3fc
- transaction
- 30cca2308b0e2e40f2efa48f1ba46d24d10e363ba6bb0ac8cd8531c7fa3dc6f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49645
the chainentry 49645
- sealed to the entry before
- 0233214f1d4ae8e086fb1f6f281aab19c6b38774fb7a7209f2cdbd292c9198c3
- this leaf
- 59ca4e92ee02acf73497aeb2558aa2613e42f53fb145bb5bcaffa168ad89ab43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rltJiWT2lVaFgmBxPYpfMA2xoFoN5yOoVR/2qIUNtjVvoeDNTkEwYyiV30pDJwiNtj4oNk+Gqv+kDtmiNcdNDw==