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
- c6edd2e094815044c8ad6ad8a126c28c07e2d0a333761ec3f16f4fe913c7daca
- request
- ee80fb821a10c6e9c1b2b64ddfc745dffaf060a7bd1c98220240a6120c03fd8b
- transaction
- a639ee29ce29357f7a3cab3c401af57483b062111f996a072fe4f758936d4a01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14543
the chainentry 14543
- sealed to the entry before
- 6722d62e213fae464d930f4f5f5bfbc8d6e2c8de15043dff5af7914b1a7ade00
- this leaf
- 5d3671454836775152b29132eba8b5ed7e7cad0637b202e645ab36c510091c78
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- twrCnrxzNuSQTbcVXHahxgj1mat5QnoOMHncwe2abE3sKDwxIGHvcXulqz4llAEPdVCmx1/Cj4tH/VwIroFRAg==