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
- 161dc69ad53791a3f666b60c8dfa74a25304a9b10bfbab0bf9cd9a20786c1f46
- request
- 65a0314fdeffcec45bfb4494ad5a9b7466ae61e8d1275567d4ee5b901dea1219
- transaction
- 4e43715a81ef0876fc462486f5052e0563ecf322c7c8d01fa746a72fe5f113c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71966
the chainentry 71966
- sealed to the entry before
- 861b64f1eb581c3e3a7e0451c8349283879b3f596a04bcc783e5a8c74081e0a1
- this leaf
- 05c2ac35b15b8bb11bff50742c6f933bc09ec7c980e6ac3c508b9653115f0484
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BWWs6sDQP5tHeD8XkIMa6NJ0PoPFiw/sk7Boa0LLT19TYYDV//1y8uqGAaDwdFIZdRWQLchh67hE6pwsEnxaAQ==