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
- dbb3fedc3415f766e36470dc13f831ad8d98a2217e1fb26b003c68c419e394ff
- request
- ca98ef8cde06f386483c21a4ed63adfdec89a2ea4b27ba48076239e3cceedf28
- transaction
- d6a0a2f37e99669653f83013b1670f476e2adeb5f71d57a06f0ad345fc59d37ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53892
the chainentry 53892
- sealed to the entry before
- efab6da30b86c11a0f673520e35d649f24dbb86dea77b92e64395fa4859b92cd
- this leaf
- 653814661d9fa777523b197213438fa1fea0256a49b6de8dfacb6e03e85ade7c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7tBCq45uDPD9yKn4B1ebrNQ5jUXZP69JKUDX9zkjuMUA+cLVW/kWs2SYFuCprGVoi1nrUS1Ie/+Hp5Ca7q7ADg==