Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckME<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=55.msg1598#msg1598">Quote from: sirius-m on June 16, 2010, 08:26:14 AM</a></div><div class="quote">Yeah, I meant to say that cross-domain javascript calls are forbidden, so you can't call 127.0.0.1 from a javascript that doesn't reside in 127.0.0.1. Come to think of it, it would be quite funny if browsers allowed malicious cross-domain javascript to change people's Facebook pages etc.<br/></div><br/>You could do an iframe that pointed to something like <a href="http://127.0.0.1:8330?">http://127.0.0.1:8330?</a>pay=domain.com&amp;amount=x&amp;return=&lt;wheretoreturn.php&gt; and then that iframe would contain a little bitcoin interface stating how much &amp; who you're paying and a button to confirm or cancel the payment. If you confirm the payment then it sends the coins to the domain and then redirects to the return value in the query string. bitcoin could add a ?paid=true or ?paid=false to the return location as well so the return script on the domain could then check if it received the payment correctly, or cancel the order.<br/><br/>Edit: the bitcoin interface should also have a password before you can confirm the payment. Otherwise you could scan for port 8330 being open on anybody and then automatically have it send payments.</div> text/html