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
- c867f2243d4350d9c84267cbd4aadd64160f32d9118b28b51f2d6237f20632e8
- request
- 7fe99d2c7527ca430a0f0b3c0da8d3d5bd0f167467cace46ec925ebb8598c373
- transaction
- 595c932bd26d54724c38e61653e0ac0bcf3d9ec1b5ececfa7fbb41969dde2e38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56615
the chainentry 56615
- sealed to the entry before
- d4d1a1f4d9d002c7ce8331bd791c5988ef8dbdcd1c7b7b3fd7aa87de4e881576
- this leaf
- a0646e11abb4b2c91f71042ec8a40f24fe2180e408436614e0c413fe6cfd96e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U9OPhkMOuwhkp1YKdXV1yhNb7ARvepGUsrcZ5FrIPA1eYi7I+9/5pb3FSW0RkhhVfQRaIHCka/41MlZPk6+LCw==