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
- ed8041fa745af3bc1cc64e8e65003ee33c9ca2fb079273f33b1a82a3aed13123
- request
- a261f2a41a1c6d8639ccc6f560540d9b5eee87786fca8bf41850fd2c5b9f9b54
- transaction
- c8657736131b0c8e7ca4759f1d3bc6a7d7ba91dd1ccdf906188aa688a11acf99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 141
the chainentry 141
- sealed to the entry before
- 63642a9ae9586a56e6235d55daadb02ca162ba946fc3d1217ea6ff25169e1285
- this leaf
- d27a3f0d8aa44aecf6facd3d3184fee92af5383b766ab4ad168c99469e1c89ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HOPk9VOeti5mfsEmfnZrXXLJv5eCRzCN2RI0stwp9HRn5RqUOk0VhYatysYD13dzr5QVMksFgp8ZME/hB9fPAw==