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
- cd66001cb396e509aaec1b95f88c979f5f0a471d58221df3a70bcdf195a92c80
- request
- 325b53154915bdbc2806f6d11b6b68a4f394ff7530b6157684bcbaad6c4721da
- transaction
- 88ee03b6d13c522e79b167ba807fb7b383f511b726d54c5d6376da2c79ac7af4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9435
the chainentry 9435
- sealed to the entry before
- c761121106948720dec758c9e9612fd6b1fbd313d2c27f774419889a7e04a737
- this leaf
- 295844cc1cda8a3e2ea8d8addf9c1fa9e64127eff0c52f71b958566207597d53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zbJONCycbDHMbN59zMhGLH8BMCbUcEuhukIVZf8FgfZUz9iTugF+/wjhVi7NfBXnEjazVRpH3MYaQHb6mNeOCg==