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
- a17a551d971f76e8896e7019cdb068dd51651e2f951fc11e74f7828c939c1d78
- request
- c4a996a06e1bb0ed6ec25c05b5d33ef92b57192316e4176c6d327be521a829d8
- transaction
- 9c7ee5ee74cd57428837033dc351f4c07ef834e8ad77e8d5e9c24108a9334d0dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38114
the chainentry 38114
- sealed to the entry before
- aac0630734c881e7ed622b771a7f5e67fb81fd935972b1572c2f6eabb3f3f727
- this leaf
- 999e1fc2bc8ae44d9ab465a1b050e3d24c0b95070bcd456af0e9c7293c6c3eba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2WGEKCQHZ/8IFcL0RcdGzospaeYoJPP/aVKc2XYSfEUXRzFXCMVGK3iV5t0I9U8DuvaKWZOQovudIvUSEsPVDw==