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
- c1a7a7b8b7af2753a316e5fc645ae03eaf1f89e1de52b3681e2a73f0e39043f9
- request
- 9e99817f01ded6a4c90e49d411b3d0e330860f3835270779a0b89e2623246958
- transaction
- 7001c66141f4f73b19a84dbb916ef858bb605857eb057f7f024361d889b7492dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31919
the chainentry 31919
- sealed to the entry before
- 4e10b3e2eecd5aa6328707e1f43f1efdb630e4c679bd99c7cd15b5f770dc21cd
- this leaf
- aa44e4d709045030bb22abaab924c620228a2cea9bca36444833a4bbd752869d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7J0gue6T+7gFORZUYR7ObeuLmcFDNYGhI336wCpGl846qcg5ez/KavEzI5sRqhFdDOMn6lfTIrio+W7CHkErAQ==