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
- de24bb0afee290ef74eb5bab360cfd11d2a70ef496d972b6e640a1d2e1222c58
- request
- daae626a3612cc7aa14934e9885d78ce7b873b09ef9e80331d2adf81b32e1644
- transaction
- 33a3b7c26b9cd0b870238d4db876b789f5225a0c1865876032cef1c27262e1c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58987
the chainentry 58987
- sealed to the entry before
- 61d0acb21b9102f60bb8db0314af4aeef2ed802206f9d8c2de3ee49d7fb34945
- this leaf
- 1f97dbf18cc7f073bd4a0adf4cca002ff350d244f69e2f18a9b655e943546963
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fsvcgyIYIa46zrJT2B8DZdsrwIIQYvHWEaeL62HoaMmQFh9OmAYNcsrir1L7Clx5fsmr19MxbVsSkFHwA/EpAg==