You may pay someone to create your store, or you visit our seminar and become a professional yourself with the silver certification
Started by spinfx, February 06, 2006, 05:51:15 AM
Quote from: UncleBuck on March 29, 2006, 06:57:40 AMJust an update for those who may be interested in the St.George gateway:I have the configuration working correctly and have used notify.php as the basis for a new file called stgba_notify.phpTesting sending transactions to the https address at St.George has been working but as I am using a test database on their site, the response verifier only ever returns a FALSE which makes it difficult to test it properly.I have been in contact with St.George asking if they have a transaction verifier for the test database and this was their response:"As far as I am aware there is no Test Reponse URL but I am having IT investigate this at the moment. Most merchants test in the live system."(not what I expected to get as an answer)I will update this thread as more comes to light.
Quote from: UncleBuck on March 08, 2006, 06:01:06 AMBuild URL and direct to St. George with basic infoShopper completes detailsOn payment completion, user comes back to site with basic details of payment (tx #, amount, merchant id)Transaction sent to St. George URL for verificationDatabase updated to reflect payment
FIPN is a class library that implement core functionality for communicationbetween an online application and online payment gateways of finnish banks.General notes - see this READMEClass documentation for developers - see /doc/class/index.htmlChangelog - see CHANGELOGLicense (GNU GPL) - see LICENSEPractically all finnish banks offer web payment method for their businessand consumer customers (Luottokunta, a finnish credit cart processor,co-owned by the banks, offers a similar method). These methods sharecommon practices but implementation differs a little from bank to bank.FIPN takes care of these differing implementations. It presents a similarinterface to all different banks. Thus the client application doesn't needa large number of different payment modules, but only an adapter layerbetween its shopping cart checkout process (etc.) and FIPN. A change inclient application requires adjustments only in the adapter, not innumerous payment modules. A change in bank's web-API requires an adjustmentin FIPN, and in worst case in adapters, but not in numerous payment modulesof numerous client applications.The basic common practice shared by the finnish banks goes like this:At the end of checkout process the e-commerce application presents a HTMLform to the customer. HTML form's hidden fields contain data like merchant'sID, bank reference number, total value, return URL and a security hash.Different banks require different additional fields and the field names andproperties differ from bank to bank.The customer moves to bank's web payment site and transfers the form datawith him as POST-method parameters. Bank verifies the form data. Customeridentifies himself using ID, password and session specific second password.Then the customer either accepts or cancels the transaction. If transactionis accepted, bank transfers money from customer's bank account to merchant'sbank account in (almost) real time. Bank redirects the customer back tomerchant's return URL passing information about the outcome of thetransaction as GET-method parameters.Instant payment, instant information - thus the name "FIPN" - FinnishInstant Payment Notification. IPN is a commonly used term on othersimilar services like PayPal.FIPN is free software. This version may have been modified pursuantto the GNU General Public License, and as distributed it includes oris derivative of works licensed under the GNU General Public License orother free or open source software licenses.NO WARRANTY! USE AT YOUR OWN RISK!
Quote from: spinfx on February 06, 2006, 05:51:15 AMWondered if anyone is working on paytment modules for the major Aussie Banks, particularly Commonwealth Bank.
Warning: this topic has not been posted in for at least 120 days.Unless you're sure you want to reply, please consider starting a new topic.
Page created in 0.129 seconds with 22 queries.