If you use SagePay Form integration then you might think that it is impossible to release orders created via this integration system via the API.
Historically this was true however thanks to the new admin and reporting API you can now grab all of the details you need to perform the kind of admin side integration previously only possible via Server and Direct integrations.
This does take a bit of work but if you like the fact that Form alleviates PCI compliance issues, allows your customers to use the nice easy to use Form interface and also gives you easy PayPal integration then this is a great solution.
Thanks goes out to SagePay’s technical support who have proved really helpful in ironing out the kinks in getting this working.
It appears that all the paypoint (formally secpay) modules have vanished from the magento connect site.
This is a pain for a lot of people who have chosen the gateway to service their payments, and leaves two options for most people :-
- * Choose a different provider
- * Get a custom module written
As Magento developers we’re happy to quote for the latter option, but we expect a lot of people will go for the former.
In a follow up to our popular blog post describing the process of getting AMTU 1 set up on a Centos server, this post describes how to get the latest version 2 of AMTU running.
Things have moved on and thankfully it is a lot easier than it was.
Firstly get Sun Java installed. You will need to get the URL for downloading the RPM from here:
Accept the agreement, download the correct RPM version and then pause it. Copy the download URL and paste it into this command:
rpm - jre [hit tab to complete]
Now check the correct java version is being used:
You should get something looking like:
[root@94 tmp]# java -version
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b06)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)
Now you can install AMTU
chmod +x AMTU_unix.sh
Keep hitting enter to get to the bottom of the terms and then agree, agree to all the other options. That is AMTU installed.
The final step is to configure this using the CLI configure utitlity.
You need to create an xml file for the AMTU configuration. You can see a sample file in /opt/amtu/xml/sample.xml.
Lets copy that file and then edit it accordingly.
cp sample.xml configuration.xml
You do need to be signed up for MWS to get some of the keys etc that are required. If not already, go to this page and hit the sign up button.
Once you have updated the XML configuration you run this command to apply it:
/opt/amtu/Utilities/configure SETUP /opt/amtu/xml/configuration.xml
If you get some error messages at this point, edit the configuration and try again. Once you have the configuration set you can start the daemon.
Thanks to the acquisition of Magento by eBay, one of the major extension developers, Ess, now has an agreement with eBay/Magento to provide their integration extension free.
Here’s their site and here’s the extension on Magento Connect
It’s also worth knowing that the extension is avaiable on Magento Go, so if you’re looking for hosted-only, management-free eCommerce with integration with eBay, that might be an option. Remember that Magento Go is not extendable by third parties though as it is a locked-down solution.
Anyway, some of the features of the extension are :-
- Stock Level Synchronisation between eBay and Magento Stores
- Create eBay listing templates which can create eBay listings direct from your Magento products
- Multiple eBay accounts per store
- Automatically leave feedback
- eBay transaction and order import
Stage Gear – General Site Improvements
Stage Gear needed a number of aspects of their OSCommerce site improving, including the look and feel, the addition of SEO URLs to improve site ranking, improving search on the site and adding basic Facebook integration.
Stage Gear is a company that specialise in retailing sound and lighting equipment for use by clubs, pubs, bands and DJs.
This project was terrific as it demonstrates that OSCommerce is still fully capable of running a modern web site.
If you are testing out your SagePay integration, you need to be able to input some test card details that the test.sagepay.com system will accept.
Here they are:
or testing transactions on the Protx test server, use the following card numbers.
NB: there are NO dummy cards to use on the Live server. Actual Live bank cards must be used.
||Protx Card Name
|Visa Electron UK Debit
|Japan Credit Bureau (JCB)
You’ll also need to supply an Expiry Date in the future and the following values for CV2, Billing Address Numbers and Billing Post Code Numbers. These are the only values which will return as Matched. Any other values will return a Not Matched.
Billing Address: 88
Billing PostCode: 412