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
- ee31b4dd1ab2591c2caef887b398169b476f76796ea9217d9e83d96b664e4b47
- request
- df10ba15c82b6bceadbfcec7a87a5e406f8ad6f4258bd17344803af64cfc68b9
- transaction
- 0809aa104a9dfef7f738c66ee42e1d88871e99229f3d6ab7051d9fce2d2d5b8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21115
the chainentry 21115
- sealed to the entry before
- c0f37ae905dfa4998b6a64ad7e32e835c5b3165cad930f78e21fcc808e64152a
- this leaf
- 2e75936c3c17382eac18acc37b9ad7586b3f263431632d4f0c8e3da0de6261d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IXeUygxfY9EApBLMbTLZC4UCAHQtweuwztUfyE8VsZjdj4lWO3r3N+lR65nriGryyh95TEdABeBZkkDmm29mDA==