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
- 5874fb56e27249e6dbd7e315ac0cd74cc23455edcf46a1db3c642aed1f96aba1
- request
- c7f02bdc957bcfd0c71a95c16a516177bd75f556cfb3e41f6fa1a53d9271466c
- transaction
- e117653eb9c30b22a39872a80175976496290d3749d955e9d3244946f4596ab0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65672
the chainentry 65672
- sealed to the entry before
- ce81ba5e54fd75dfb0d179257a569facab50cbad5ab2e3d4ecdf5ac3b1cadb93
- this leaf
- e02e5e8ad0bec0de7fd94ab4d04c92fc7fc54e205d4ecfd833225838cd0c2aaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Va1wr/isHDSLF8OYJwkp0zSVYgL2hkTIji8NrEa9f2GCtYwuAgotodCTEHwA4530slJ22QazwijTbyv1UPYADg==