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
- 3819182661143b103b86e292b6d3904656869e976fc1da02d9b8982a24c0fff7
- request
- 4b16af7bef752e833ea8df5567635d0eff8c062a1b41075b34baa17b928b9e40
- transaction
- 457d46cd26c51cdfbe98aca5015dbdab3190b45ca6576870f9ca3bedbb107ec9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9858
the chainentry 9858
- sealed to the entry before
- 1fe689b824f8c27e66c82677b49bbd6ae6a9a6adc6e801f4fa08dec8b6533d95
- this leaf
- 2c113bac00e397f929a88b696796451c5cf395394facf72eb5e2398478a9df1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xCZMO4W7a7DoROc1lafupj351fYfcqn1OMA1oyqKJe3e6q5JTfXeW007k+c6qiSjxaT4K90bk+F+kpqFpsuMDA==