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
- 5e1d70877d0e52c1eab2e722859dcf68198948b8d11dff406383f25aaa47bb9e
- request
- 3fa46f9e07aa9f85bf80728fcb0cc42a9e02fd967c8457a38a60c020133707d8
- transaction
- 0bf3a3cec7ef26d34de31332e0bf982d62a7460d2e36c248b6e62624ea2389cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2250
the chainentry 2250
- sealed to the entry before
- b476c5b120e41ad2ca3a1547514eb670d00df68454c5f29765f7edff7f76ec0b
- this leaf
- 40f0684af4f4f13be1e8c87ff9d7eda588d92d2ee7aae8a7f9bd0dd5dac1290f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u/oO0rhFDuVT6iOLy2LPWOVsmA4kAT24+khk7rlmZ7iwl2jJqRlzuQBAs8Nols6AzTWYffM/tdRkFOm3fOhQDA==