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
- e3d0d0165d93d78d77987f33273659671064837f3a7b4d5c3fbf4c0d12b6755e
- request
- 34900e521342def7697920ccd88f7e47692e0e008ca28aaaab3b44c81b5cb43c
- transaction
- a1e96998082a90daeb6420132b60438a72a75585c8acbd1150020709fc9fd8b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19899
the chainentry 19899
- sealed to the entry before
- 0bb7f7fc75a2ff22f02892a2c5f53a4dd8920f3d92817a1e22e48a737688a585
- this leaf
- f2783e7e102564dea3da5c09f6f8baa32ad3bec75858971409bf5176dd1a797b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vZL1A1IS9Qc7VE0+ha0prGfMs/aVYblf7HkrVHzbvliAXyF6Dw19z0iy0iSvBOdrMsFK8gqugBvQYlt0C1IoBQ==