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
- 88690de1d98642fcb242bd2a15f6b56b3de5dc3652d12892fc3426f0844ced3c
- request
- 54d27ef438251ced83b630c01ee99772d5389e7afe637e076c7296e1fce0ac59
- transaction
- 1f3b9fb4f000eae819472250b8a0c0ca75c0f53ea0a17857fc902f5edbbce4dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45552
the chainentry 45552
- sealed to the entry before
- 0773d3dc7c4873977f7377f6cacfd461bce9f7a03ee404c6640e314b309bd90b
- this leaf
- 218468589a039a6b80b33f464c9e3828dc2c15cd2ce609d3f17de60103cf24d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e5gqg6fOJqOY2YgnW1gFK1Dfo3Am5fvp3TFsrL7dII1+QLck230o6aqu7930schrfPSdaCvTYfD2laGiCLlXCg==