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
- 57a7c0542bcb58a201d0111875e1fe57fd73d21e3b6c54089eb75557e73abfbc
- request
- 3ecd42a27533b1e788af1b6ff0c2cb5132f6f616b8a16c62090c77e00e0c7fd5
- transaction
- 99b75a1baae7d5d3ced787f4e7f90223eb602a71108e5d3230e57d09d1322270computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42227
the chainentry 42227
- sealed to the entry before
- 8a39e6c618738bfc3f9ba0dd87de552f3f358a5ae46fbf8de4089aebd696e59d
- this leaf
- c3e9e88bc710a99837569b670192cb2e2a76b538261084a631daedb02a8b61e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yiIk1EdgzRuDaFAdmA3kbGWdPAnMDP+hdSJNpdbXsKUlAkqrSk6mawcRzo+K5LepNtg8jNfP5kQfmtypgZtXCQ==