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
- 38912743d104b3ab67fc9b86e50b6cfd3a3e382f497a1643e1684fdf4de4c863
- request
- ff007ee77835d2a22ed0d5074f7eaacb92480b1613de9c6d36fc8db8e0d8185b
- transaction
- 0bfada1b66e4fb3b397ea3d58cad21bba1fdab084c4894455f0ab94caf20f63ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24448
the chainentry 24448
- sealed to the entry before
- b32f8e943a981e3855432d6fc45821fc69b44fe79f2abca2075d9078c7eb6949
- this leaf
- e1e3b256c07a4205c82b58ba9423ebecc33a3a759db855b7466fce92bd5b3746
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hbhFLJk8k6TNXDN0t73cGFDy6y7kADOHJTuuNC6kSh/xIlnmz3l0SCsdKYOT3TF+KdwANiiC0p8qn3Ja3hxtCQ==