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
- ecb71452a94e784f00e37add5247edd0f2fba4b10a367d05922717b3ced52c49
- request
- 4408b595cdcb5518f6f5c8569191af32f79d1f20b7a680d35f3bb28da162950b
- transaction
- 106e344dc6674827a6351a5ff53702821fb841112c6989860fa6c3fa8ae07fb9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38363
the chainentry 38363
- sealed to the entry before
- 271f8641449fb54b551a0cd1d8f55f478e193ffe413cc539041f8d69ab0fa21e
- this leaf
- a40fd055e144f55976affcb204102ce3d74863a5bad4bc6667edf9fd6f93b30c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6BgiJskjV2mlWWATbW9Ium94j9xOmWOUVqjbyRvyzAQgHKb7+0zgst6S45D1y82wzAfM6wckdy7A7HewQe+YDw==