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
- a515df587d4aac3942fe1613e1b4771ff1ce694775520689213c207603bff24f
- request
- 397d2b1bb9438b916e2df9b9f01bc32a6628da5f089b48409a55277ad71254bf
- transaction
- aa6252cfad048e3c1afbcd32bb6ce8b089fd965ff31f77be2656407db4c1728dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 451
the chainentry 451
- sealed to the entry before
- 02333fbfe0230daf736dd705f53143baa6d7339ece3de9263833d93fc65a2994
- this leaf
- 841b4adf421e288fe6f5acd49682c4fa2f49a18c338d5b6081e500e89c43602a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fakj25YPjgYeDaAHFuQuFjEF2HdKjKBY5P/2cEdX0ZGaZkcwhq3YJSQNtOMNlphMd6dxFinzgDGO3LwncHy4BQ==