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
- 7299bd1f2ac9a45edcdb7367f9336e58b55c37c0097e1fd3f061e5b041679c33
- request
- a14de3e4cb9e3fa1566100246a167b67632eb57bcadd7b51bd279b0cfb98aa1b
- transaction
- 1947e9f1b83d087ad7c0c38f645ac9a25de3a5fa11060efaae86100ba0579911computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40010
the chainentry 40010
- sealed to the entry before
- 9a9de9f152515201dfa9958141d28401c50651e16099f23bd54f32907f89dbd3
- this leaf
- 9aa451e17e54b21410a6c104b66da45301ac5a08dfac77e321acd0120fc7e9d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SijjlCZ2EaqwCq4aiKDkSebCN8GWjVzkVNG9IifMUdeWLzy2TbH8Eq8YjvO3DCw5P/mM+BS6nALnEmUm2susCw==