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
- d47654314bf3170152a3cf3b8b3f055f62f58dbf9ccbeab34734fd6e9519eafb
- request
- ba8832dbf29f6ac2caf5b1aafcd38f2cc0961880bb27c330993e40be5c9680da
- transaction
- 6f8cd9cc91aead6b89c611ff09abd89e2e4aef94c4d9bc8dbe1e61e31b986802computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69860
the chainentry 69860
- sealed to the entry before
- e4b58e7e49daaa81b0579e8514af4ed06586ce22af3817aeebdf48da8e6d3439
- this leaf
- 915c3cf6c81977b326e7c48ac8aff766f2989f9f238007fc22f9ad34f3251dc0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lVdN58poQPl+w48lc4+QBTbJjoUxvqdBO05xeKYe2DVlkT9H8Trn7F7BiMF0R0OOPEI6s1pGoZkBO2Y40IW6AQ==