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
- 1c11a804bda694f4fc42aab526dad04e6bafd82b57d8aa997877951d8443b121
- request
- a210ccccc317f5363f16a860c3d29ddda57735aee9bbc410db59ab7fdde66bfd
- transaction
- a3d89667f764e4ea343ae5496d4626f27eff4a3268d84e5b79e83c126ed5c77ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61095
the chainentry 61095
- sealed to the entry before
- ed2ac38acff1c264e42a2ed90d7410ad0dd0aa0d697f272fac75e60717df9486
- this leaf
- 8947e4ba9bf65501848f90f783fba5363f0cd88b5e6d848f9baf03edcefbac29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cup3Ku1rJFdE8zgQPYqddft+e+qubfYIk8udPeK4suv6nOO4x8DN8KpJLLweVCAd1fGWuKgwWEDk7v8vm+l4Dw==