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
- db57b34aea4d5b757c279894cfebbea0732c040bae2c2c21ebe2faf7493ed5ad
- request
- 3b3f5f6231bb75f1ae8fcfba16e532ffdefdd04ffa6608e8a4ecc173e8c3a71c
- transaction
- 41c63f3f9720c776061fa6a692a1723b4a7dec158f82984e632d9d07278a149fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47768
the chainentry 47768
- sealed to the entry before
- 49988010cef1034ed5a304be4c56cf565d2b1de2074ee046d5dda84c0f1f3783
- this leaf
- eaa1c2a8428afdae183809f6ebda2587135688a0d806f6718c57d1941eef4d21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sHaNfQJt2J2K72qS4RH5Noqou4khTcg8Utf778Qh6aeBKRJsGri4bJ5KiG2Gdzgs/3gJTKHBOKvfCR126/a3Dw==