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
- eba49cb344efea97a7a1563656a9c24e0462cc5c4f78227a119722a13c9d9692
- request
- b22db8707d736c81f8eadb410ca7ee7e0dfed45700ea8afd04fe63dbfb640b2f
- transaction
- f8015f30e745b48f17fb0e343d02724e450b23a614922ce68d10e1de3038e284computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13307
the chainentry 13307
- sealed to the entry before
- b3318602f80588f90ea68cb2453af38430170f8f994d56a82143c59d6e80ec10
- this leaf
- 0eb7333e139653a3118d6a5f5d1f7cd0793a3dc0692a9517d849a23db7923324
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r+aEcMhj6K9qEJUQEbcGGnhJrAeoNvLJ87rnCKcsbQGG3vQGIjaj08LlwK1xXT+l0mRRNndKesrt1qkDtWhmBA==