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
- fe93a3e01ad4c805f7c9a590759640537cadd5fd4835e31431824db84499a7ec
- request
- 3c99482ba69e667b72e7709440849f1698dcfb9866de22d246052dc53b0306c8
- transaction
- ec9f6fef0f75ed9ef422ebfe250362142507c41e9742da88692d1d7d7e593cf9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10776
the chainentry 10776
- sealed to the entry before
- a600c6172fca9e4d7d3ea3864f134b2678465dbfcd4bee66c1b14a05047d2266
- this leaf
- 4e4cae6f02524e98e7f0c60b633f680e2ef2cb8c079992cf5be7d09d526e0fab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lCKbhUlCZPYa7GyUD1Pa+QKYYtm3c85borD9AKzEsALUCxlj3zbE3dZwEhhJElnJ4AWmBKEWM59w0GY1M3D/Cw==