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
- d0a20ec67005c0938d0c80347357cd5ec90fc9f154b6a9d3ff6acd6cef684357
- request
- 00cba3e16a8103b61f5918a328ebe13a47f7c5cdfb8188777fe1c42c43db8a8a
- transaction
- 6cd5a6860904c8685be8aafb6322703efbe230e21fd9c841f5d1f05986a8cc24computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7932
the chainentry 7932
- sealed to the entry before
- b9bba9c44377b8bb075485d271caa9a043bc420a207c9ccd47521165cb3fa80c
- this leaf
- 43d42e362d7c0cd6d287bf2b5a60ef1e69aa116973a8e33e4ca2683f8af28a9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kCuKAYvie0M9TgpYecaYUB8KB661Df9O8BVJ42ZXHxOgudrgWRifAYbbHQh272nqYDFAIJhJsezh5YM6ED/vAA==