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
- 454517d681a3998633ac0b29c0adf8a8dade121ee46ff15b53e11c838994de63
- request
- 429b77cdf2f602c8538001c33639ae4e45154537d4b0acee3bfddbf6ccfa5188
- transaction
- 18a7e9fc10c9ddb3d34f808556443eb87da6bbe522037d817ea189962063fd4ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64520
the chainentry 64520
- sealed to the entry before
- 11a2403d8ebf7a06d88eb128fdc179e5b03d48972682a9015bbd4447b33a2e03
- this leaf
- f374619c9c439d14243ef8194a67fc651c39ebd83bcfa2966a037bf3bf7241e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HNYymam1uN7+vlBZa5uIOxWa+95JFlbYN8e/yY+qdXwlSf1XBkchDVvoVoA6E++1JmrHGlXFcAKTSkkrE809Aw==