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
- d1f6dd792c818f2f4275edf8db2c3ebcf683a0f93d2df005d0cd6161f186105b
- request
- d91e1e581ad1f4986c4e41d24627ffa7c3a81aaf6f38c92db927e31cb1ae5764
- transaction
- a43afa3efa4ba35784bbafa3630495029977111c3ef1f86a2173794eede8c530computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41005
the chainentry 41005
- sealed to the entry before
- cbe3308dbe5e6d9131352d2b5b5478750bba4e1d581c4988660b68bd4d1ab8dc
- this leaf
- 2a8a22e7f5707f7c601047e13648c07c0e58c8d977cf5b5af532bf237c2fac3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c7hbsrCxxlepNy0coZwJyujnuBuGKRPPjdB70EH65GuM1kbMogkiW8xW3rz7MHqn/ms6xTMWlNtYU5gzIiekAw==