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
- e58a2958bdf1e74aa37eba9d2811c4244726a764a9486d6b64dbf652e4d87ae0
- request
- 81d44bf226300b77e5d6e90369ba04c06c43fc2861ea9f01a1998350c57c8895
- transaction
- b564ebf7b70c0ba32b5b1dd9f1b6999af9ebe307f74009ab358900fd1e8e8f9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28138
the chainentry 28138
- sealed to the entry before
- 851411b7575c44f5a7bea438f03bce3ec474b6d655304f2fc5df49433d9ec844
- this leaf
- 07ce1e6ad4a1193a2261f0eefbf5a0a168e9c7b6149aad9015894fc5aeceb455
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dGSTP4Q57N7GDzKHgHmp24PIT3OWwhZNcS2ciVGwt8xukA6N3nKKGf698VTAYZLSiYVidweVKa0MA4Auj34FBQ==