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
- 6f821281fd55a13c2e74130617684ca20e724efb46acf76769261cfb84d188a7
- request
- 566d2da70fbfa4fe7ca66adf0d858aa0e3a5060137b45636f23ca2c3e7cbd01b
- transaction
- c0ec5bb2aa182d11d27867ba1111869a1efaa8c25f1b8512b433251bbe511566computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20200
the chainentry 20200
- sealed to the entry before
- a2afb7b6951aedd8fb0e7c0a797ce53352070ee97c823855a449523fe261fe80
- this leaf
- c8c3aa2383e4493bb932e8137f0a74b5b098c3e8746061ea77a90ddb80b3646d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 13kSHcV/0/S/jnihKbqhuoUE80pIZGRLKHnBlJwq1r5yMBpYIZwoXw7+/oHjrVjchFQ38LgtdXQjoMNj1C16Dw==