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
- 174628cf590d33e846ea7e1ac3f03394517067b158c25b7cd1d5caed5b46bd86
- request
- 3cf5ec53a6725829bab4ca3cad3b3c84325e1cdfab95e0bdc7b526e05910309c
- transaction
- 4d79ed4e171413644a9f2b1555922d660bcbb44188226f414c385004ef980918computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11875
the chainentry 11875
- sealed to the entry before
- 769f29df4a99cfd65208b1b63005c65c484227d10dae143440d173c894efc447
- this leaf
- 9001108ca596d4c788136e4a4bab06806e137240526e246a2bf755ee468cb46b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hu/nJFcutFA2/+OjQ73Ku18bApjatx6aVBsuVD70btbnQYWtI/VuSQTd77H20RF0A+VTDtE0G77lQgxoHh7jCg==