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
- 0e42fd2c98db1fe321db248e0818caf1e15c5649f4cd2d52719eed97164183e9
- request
- ad0b2ec81ac422dea24ba893be8d914177bdc64f47aaeabf85568f85b973885e
- transaction
- 0a1d758c828980d1e5a2be1f5b76724317737207b949c8eb5eb96b73bd7317d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32042
the chainentry 32042
- sealed to the entry before
- 738f6d26456ad3119890060eb9379e71262b362d8b93bd47ec0efbb24f609e03
- this leaf
- abb30ad7f592c9c6afe9f94b83868766e06a0172b26a8ef8f4f96792fe592a0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3lpmH7jc9/XrwcGcaglAFivCgF4aJW8+VuZpiKTXl/GGtTJ1weTW/LfMU60Mtf+rwj7XZPnu64cmDIT5llLdDQ==