I would look at the authorize.net documentation as they present the most generic methods for HTTP based authentication.
If you are talking about a client-side processing solution, it can be accomplished but a bad idea. SWF's can be easily reverse engineered exposing API keys, hash entries, merchant account identities and credentials to external access. Traditional non-API Wallet approaches (standard PayPal, Amazon FPS, Google Wallet) cannot exist in a client only solution as they require a post-back URL with which to transact. The only secure solution has a server acting as a gateway to the payment service with the Authorize.net documents providing many resources. Other payment aggregators offer likewise documentation such as Cybersource, Paypal (both Wallet and API). A server hides the specifics (code and metadata) from the peering eyes of those interesting in subverting your payment service. KFB From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Scott Sent: Wednesday, March 04, 2009 7:09 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Credit card processing in Flex Anyone have a website or information that references how to process credit cards through flex? Thanks Scott -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , and is believed to be clean.
<<image001.jpg>>
<<image002.jpg>>
