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
- 0ae81d259921341cd5801438b7af193e06fbbdbabc8bd1f5089a61f459bd73a9
- request
- 169aa0c8e7a68512a69ff8d5a3feecc8b2829f7c78d81054a4743796b74ea217
- transaction
- b7a58cc61523d54c09feb4c946e1287afe6d355a25b5c3fa9f200e2e160c7d90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30424
the chainentry 30424
- sealed to the entry before
- cef6820e9356d7c7df404b095cd46b67033e002da34f7951339dd7beaa3c7b79
- this leaf
- c450eeeea88b24b10d8e27edb69145f0ee5542ce05f75d11b6610966379821c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ltefMl5lPF8tvevY+d5FDj8HC9u5QrIqz7Ua+SZqPVVg0zfnw+7E8JxnDLRooucOveN8vHpoAjCSfShnLXwnAQ==