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
- 58aebbca0a74ca934b8780495fc29a6ff88b88b548afdc8e4d7e4ff6ee1fc869
- request
- d5b400fdfcd0fd5bea796cdeb27ac790036c64a5fb95c2f76592e26727cd63bf
- transaction
- 61883c6a69b1758c456ca5dc65ff09f15787cad7ee7706d439eeabc4a842747ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 356
the chainentry 356
- sealed to the entry before
- 0282f9f329ec7cc46c72530c68dbdfe75b5e1fd1d8fe7458898842bb674e7753
- this leaf
- 8bed0a4b269cd932300a4c84f827bb3b070a8ce83259d710790524db4bd51cf8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- blYNi3PUkWgi1HSH7L7OhPe5xMJf9hOOTxBX6QsLazxVlQezDvdK8397eRhEXyLqBFjgo8DtZUZn3ZB6w8xTDA==