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
- 63db988c35b20f5bdf3e1f92a1f505dd7d6787a669903b0f3baaaf3e79dcba5f
- request
- 9a498f74f77135b19564b317157f2d9ac74d3cc1f53eee7dbf45e9d34457db30
- transaction
- c35ef779448b48c516c04d3c5ec014ceb169c3474c63e8fe67733bf477990d6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63181
the chainentry 63181
- sealed to the entry before
- 207083ea8eddc7ef68ce74bba89ddf1f0c2e98be5e0027d394a90d6a07bc6aa3
- this leaf
- d868bb5d78374a804a50e3ae58443f875af74f343cdf5bf33e1efb0fbb321a25
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WxnLDZsgRK3FUsBs1LDpPDeDGRVqZqnsub8xvyY9R0t5ZkIu9ybEoVz8mDrkGYVxQ/D/9TqA+Kk6DDUQeyfpDg==