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
- 4714f7440aba6a128e3bb9f4fafa89003a936ecd3b781c57d0855c3c2cd2211b
- request
- 2094061e3dfbd46c3f61b9103344907405c80d6172ef7d8f22449ae6d5490cc8
- transaction
- 82d80be67acd5724a522a8df40a3d694cc2555afc30ed314b941f393ca250d75computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30161
the chainentry 30161
- sealed to the entry before
- 3053a6a2bc6108eab01ecbf8e49a83ce4e40a8f0eca4aac874ea4a455ad61c5b
- this leaf
- ba5aa4280288d603fb7bbc6c4a00eed18a614564cc53f5efb07fec66bb912f59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gz6cJx2HpcSIoY9tmWMHY/hBEQxekYtZlztbnbIjVQ+fUPsD8SYYO3UHx/s69S8htJOE1E2GkZc16zFVJPdABw==