Re: [cfaussie] Australian Payment Gateways - recommendations?

[m...@ampersand.net.au]

I usually go with eway - you just submit XML to it using cfhttp. Here's my code for doing a test (sorry for the length of this everyone else).                 <!--- testing values --->                 <cfif attributes.testgateway EQ true>                     <cfset variables.ewayCustomerID="87654321">                     <cfset form.ewayCardNumber="4444333322221111">                 </cfif>                                 <!--- create XML --->                 <cfset xml="">                 <cfset xml=xml & "<ewaygateway>">                 <cfset xml=xml & "<ewayCustomerID>#variables.ewayCustomerID#</ewayCustomerID>">                 <cfset xml=xml & "<ewayTotalAmount>#form.ewayTotalAmount#</ewayTotalAmount>">                 <cfset xml=xml & "<ewayCustomerFirstName>#form.ewayCustomerFirstName#</ewayCustomerFirstName>">                 <cfset xml=xml & "<ewayCustomerLastName>#form.ewayCustomerLastName#</ewayCustomerLastName>">                 <cfset xml=xml & "<ewayCustomerEmail>#form.ewayCustomerEmail#</ewayCustomerEmail>">                 <cfset xml=xml & "<ewayCustomerAddress>#form.ewayCustomerAddress#</ewayCustomerAddress>">                 <cfset xml=xml & "<ewayCustomerPostcode>#form.ewayCustomerPostcode#</ewayCustomerPostcode>">                 <cfset xml=xml & "<ewayCustomerInvoiceDescription>#form.ewayCustomerInvoiceDescription#</ewayCustomerInvoiceDescription>">                 <cfset xml=xml & "<ewayCustomerInvoiceRef>#form.ewayCustomerInvoiceRef#</ewayCustomerInvoiceRef>">                 <cfset xml=xml & "<ewayCardHoldersName>#form.ewayCardHoldersName#</ewayCardHoldersName>">                 <cfset xml=xml & "<ewayCardNumber>#form.ewayCardNumber#</ewayCardNumber>">                 <cfset xml=xml & "<ewayCardExpiryMonth>#form.ewayCardExpiryMonth#</ewayCardExpiryMonth>">                 <cfset xml=xml & "<ewayCardExpiryYear>#form.ewayCardExpiryYear#</ewayCardExpiryYear>">                 <cfset xml=xml & "<ewayTrxnNumber>#form.ewayTrxnNumber#</ewayTrxnNumber> ">                 <cfset xml=xml & "<ewayCVN>#form.ewayCVN#</ewayCVN> ">                 <cfset xml=xml & "<ewayOption1>#form.ewayOption1#</ewayOption1>">                 <cfset xml=xml & "<ewayOption2>#form.ewayOption2#</ewayOption2>">                 <cfset xml=xml & "<ewayOption3>#form.ewayOption3#</ewayOption3>">                 <cfset xml=xml & "</ewaygateway>">                 <cfset xml=trim(xml)>                                 <!--- send XML to eway --->                 <cfif attributes.testgateway EQ true>                     <cfhttp url="" class="moz-txt-link-rfc2396E" href="https://www.eway.com.au/gateway/xmltest/TestPage.asp">"https://www.eway.com.au/gateway/xmltest/TestPage.asp" method="post" resolveurl="no">                     <cfhttpparam type="XML" value="#xml#">                     </cfhttp>                 <cfelse>                     <cfhttp url="" class="moz-txt-link-rfc2396E" href="https://www.eway.com.au/gateway/xmlpayment.asp">"https://www.eway.com.au/gateway/xmlpayment.asp" method="post" resolveurl="no">                     <cfhttpparam type="XML" value="#xml#">                     </cfhttp>                 </cfif>                                 <!--- Parse the xml --->                 <cfset xml=XmlParse(CFHTTP.FileContent)>                 <cfset ewayTrxnStatus = xml.ewayResponse.ewayTrxnStatus.xmltext>                 <cfset ewayTrxnError = xml.ewayResponse.ewayTrxnError.xmltext>                 <cfset ewayTrxnNumber = xml.ewayResponse.ewayTrxnNumber.xmltext>                 <cfset ewayAuthCode = xml.ewayResponse.ewayAuthCode.xmltext>                 <cfset ewayTrxnReference = xml.ewayResponse.ewayTrxnNumber.xmltext> On 24/05/2010 11:23 AM, Mike Kear wrote: It's a while since I last set up a payment gateway for my clients.  I have to do another one and I'm updating my research on them.    Does anyone have any recommendations?  Are any of them particularly ColdFusion-friendly?  (I dont want to have to deal with one like i did years ago with Commonwealth Bank who told me they dont support ColdFusion because it's not a significant technology) At this stage I'm not asking about cost structure - that's the easy part to research.   I'm asking about the other factors. Here's what we need:  Non-bank - if we deal with a third party gateway, we can change banks and not have a huge problem Reasonably intelligent support people who know at least something about coldfusion Can handle transactions on their own site, but still make the pages look like our site Is speed a factor or are they all pretty much the same in terms of processing speed? Are there any other non-cost factors I should take into account nowdays? I have used Camtech in the past, and they are definitely a possibility.  Does anyone have any recommendations for any others that they think are better than Camtech? -- Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.