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
- b7ab6e73040b6c3065dc7d562671ab116fc6f049591daf7ecbcec8c8eb581754
- request
- 2e52c70f23c16b32ca9835c3544eab5c6f42db6119306ffc13f88fbde6002bbe
- transaction
- a3694223847801c9681981edcfe37d0ca44ec267f7159bccc0f8cb1bc50db1c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39605
the chainentry 39605
- sealed to the entry before
- 48275282daaa98d503f9acc56e0fe0fafb665665ae3451266b6d12a17dde78db
- this leaf
- b79e9964f6f8727dc9de1cff692d6c14cc6a5d54bc264676616b5622639d759f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V68ppLJebI6fCE5Hxxj6ggHr4m56HTECI6wEinJchIDe4UCd+Wp6U+jr2eBPJMyugtUKWWlPZkKh7uPIM7PsBg==