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
- a4f641c013c143a6915aa6ce3e280c154f84f887d317885fc9528391b7345450
- request
- fbaf74f1988c015ab73850e979657d42966309f3ff168af7e1878ea96ca21eec
- transaction
- 613bc16eb6817649b3df043841d0ab21a9e9b3b3ab0ea25ad7e95668cbe6b89fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42923
the chainentry 42923
- sealed to the entry before
- ed94b64148c15d66a93d74d6e558cfc339829323cf26ecb6e62dc2450840182e
- this leaf
- c561cb50259de320b2a548db0d49ebcc02761be6a3cba19b06ff75d7ba56b49b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2BlgGxQcOSvJhyzP6wrtQo3V9dkiUpz+JfVgXTz2qENmEufKOo0bwALN3SMd1RkvSJn30BXA4zitJWbxyOniCw==