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
- e22c387b1ea7972ac83bf23e2e18a842acd7a05dec32bde9fb23250ecdc6723c
- request
- 00aaa9589f594abfe31a8b1ea0de975e763497c0ed13ea268380ba2382522faa
- transaction
- 50084bea5f92f0660f6dc350a10e719d26bb79fad6bc62a5768b03b45dcc660ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4995
the chainentry 4995
- sealed to the entry before
- 0a1d11a7cf2c81a26c2ae89f43a4154d9661a698e278fdd312cc95a10eccc4cd
- this leaf
- 582b9c985b10849dba8a9a39d48d022da7eff6baf09117f2e3516ffe70473eee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WXx6IBVVU5fVoAQk+u+5hBNulcC5gaDNque3wlUu07pokEfJkYDTBBE7+GlVei2C/6PJ1JrGPEQfzH0lYU66CA==