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
- 2c72bb34ec79f5d18cc101f3c95cb56103093ecb458ff511e31b81e22c96277d
- request
- 2a1a71030e38ac993873e2035fa6538d9f300303cf894701cd8650bf2240f5f7
- transaction
- ded4eb24d63b2f1f2e89fd0af4a44cbdeff3e64eb43a8556fa8a936194025cd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34163
the chainentry 34163
- sealed to the entry before
- 57de813d41895a0bf1241b3d46102cffcf4398a97db719839277cc49e3796914
- this leaf
- eefd29e798f6caa3b30deb16f0bc59ae83e91683cfd183eb8f4d09e4926f57c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 36dXxw//4tzi3yPALDn4WWkRYzKfdtnGWky87xOfHOLSxAcEq0IIQUMbhMqY49zjzrsRA5SuqOUKzwdqm7GWBw==