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
- c464b76e6f0ceb5afddd139e729b6e7390e26b972297ecac013d1b746610ea30
- request
- cb9601804c4e865dc3527d6fd1deb0c23633ba8816efa5ff0c7c09ecfa37aab2
- transaction
- c6cd09f7aa8a20105ea29cc16c695cbcff963d3a2b43bc12bae9ecbe2951b2becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17635
the chainentry 17635
- sealed to the entry before
- 8128d612d0792745e1420cb28827ff17e3ddad69476145881e120f8fcf0ad3bf
- this leaf
- d6a89246e593b77bafb3fe269ada2b4fa0b6f1bee541f5809e171aa0d33cbf07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oLy+lty5RXJU44IQCx8So1TH/wtaZ/jMCRbNU1Uvf/n9slG+3fEC7iaF9eEKAVD3vu7662/1nBcPNPp5OL3xDA==