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
- ec586c01e25d63dfc651897632f089c1d7411824857ae8827ae45ebbaddb6a4b
- request
- d6e0d1bd1f240dcf9b310e3f4502d9ada19033dbf3144e0a0e91239d35abc448
- transaction
- e0a385f66a404652567e15cfd3a08b92b84322e89dd8cfb0eef56c8607704516computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72603
the chainentry 72603
- sealed to the entry before
- cc36a63558ae69b6eb348f8e02256e7e4a1f28e3ddee012bdc8dd51680046316
- this leaf
- ef10aba1c666711ae5c8c06d8486d311840910f38d7bd9db3f98c3231a8f0aef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- keft+5bY+lChayzNDr0qItrxy/qH8XK8NBJ46vMkQpV00YIE9aJSRTqb3Rf4I4IpWb5pHsIWNMCV74v4TjjCDw==