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
- 54b9137a93257364dad36e993890b13b1a16bbff28cafe84f854239202ccc0fb
- request
- 22582256ca8ead497c00f3a7b9db0966aefa866e2780ebff35def096d24b8380
- transaction
- 8f0b41cc5474124a70ecab9bcdbb30b69bd2a1853b6e35fccb95b4485043eaa5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61355
the chainentry 61355
- sealed to the entry before
- 52a5c629c7fadaf63d9f6fe024de4470777340d2ca5d85bff0f2b6dbcf55540e
- this leaf
- 8d7ca8a490089c783de120b3d7adde51f9d1d17b297e011dd44148b11b05fb54
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9kQ4LZDR3E9KZpH5IxI1ctlTUXjOM4OG9QdHxcwr6LLeSNL3IptiVl6Ie17Dynf/sQo2+4QhMbJk+cCUsWBJDw==