Note: Not sure if this is the best site for this question but didn't think it was suitable for Super User etc.
I have a client with an e-commerce site built using Sage Pay. I am in the process of developing their brand new website which will also be using Sage Pay.
I am aware that if you run any transactions on the test Sage Pay server your Sage Pay account will stop taking payments. See 'If you are already set up on Live and are testing additional functionality, DO NOT leave your kit set to Test or you will not receive any money for your transactions!' from the Sage Pay docs.
My question is how can I develop my integration with Sage Pay in a safe environment which won't have any detrimental effects on the clients live Sage Pay site.
The Sage Pay simulator sounds perfect for what I am trying to do but this has not been updated to use the current protocol and I've been told there is no release date as of yet for the new version.
Thanks
I think the quote above is from one of the comments in the integration kit. Essentially, it is a warning that if you change your integration, to point at the Sage Pay test server, you won't be taking much in the way of payments.....
As long as you have a separate test integration, pointing at the Sage Pay test server, the production site will continue to operate as usual.
The test and live accounts aren't linked - the live environment won't know (or care) that there are test transactions being made from another integration.
Related
I try to integrate our test system with SagePay. But I've found lot of different apis and documentations for integration. I'm bit confused about it. Could you tell me which api version is most up to date and suits my needs?
I want to have recurring payment functionality without CVV resubmit.
System will be designed to work on US market.
This api have functionality which I want and it's also mentioned in some answers on stackoverflow
https://test.sagepay.com
This api is very easy to use, but I don't see recurring payment functionality (only with CVV resubmit)
https://developer.sagepayments.com
There is another set of documents for integration, based on .vsp services
www.sagepay.co.uk/support/integration-kits-protocols-document
I suppose some of those apis are legacy and are maintained for some old integrated systems. It would be great if documentation for those apis were gathered in one place and explained.
Sage Pay UK and Sage Payment Solutions(US) operate independtly to each other with different integration methods and API's. www.sagepay.co.uk/support/integration-kits-protocols-document relates to Sage Pay UK only.
Since CodenameOne doesn't support "the cloud storage API" any more and the parse.com is going to retire soon as well. Does CodenameOne has any plan to release a new Cloud Storage API or provide suggestions/guidelines to help developers to deal with the parse4cn1 library code, cloud code, database structure and data in parse.com?
That is something you will have to figure out yourself as parse4cn1 was initially contributed by a community member and wasn't developed by Codenameone team.
You can use a simple webservices created in php, python or java, hosted along your content with any ISP.
You may also have a look at amazon aws which is promising, they provide a cloud solution but their SDKs is not yet integrated to Codenameone.
I made the parse4cn1 lib and I'm also wondering what's smartest to do. With the announcement of Parse.com's imminent shutdown, there's been a lot of discussion around alternatives. My feeling is that "the dust is yet to settle" as per what options are best and reliable for the longer term (it would be a pity to migrate to another service only for it to be shut down soon). So I personally plan to wait till sometime in Q2 to do a proper evaluation of the alternatives. Hopefully, there'll be more clarity then.
The option to host one's own Parse server (e.g. on AWS or Heroku) is getting interesting. They recently announced support for push notifications on iOS and Android. If (when?) they open source the Parse.com dashboard code, I think that option would be much more interesting.
At some point in the coming months, I plan to make a parse4cn1 release that exposes an option to set the server path. With that, anyone migrating to the Parse server option should, in principle, be able to continue to use the cn1lib. Of course, for features that are supported by the open source Parse server.
PS: Here are pointers to some of such discussions on Parse alternatives:
https://github.com/relatedcode/ParseAlternatives
http://www.slant.co/topics/5219/compare/~firebase_vs_kumulos_vs_kinvey
Why should I use AppHarbor addons when I can get an account directly from the provider and have additional benefits (like multiple users or projects per account)? I know having addons per application centralizes configuration but it also means you have to go through AppHarbor.
In addition AppHarbor adds their header on the website of some providers (notably Airbrake), which ruins the design (looks out of place and has massive margins). On some addons pricing is much more flexible than the addon pricing (again, Airbrake is a good example - no idea what those plans offer!).
Provisioning add-ons through AppHarbor gives you the advantages of automatic application configuration, consolidated billing and being able to manage everything from AppHarbor (and not having to remember X logins and not having to remember to keep X credit cards updated at various services providers).
We've tried to make make the header as inconspicuous as possible, and it seems to work well on most of our add-on partners sites. Please drop us a line at if it causes breakage anywhere.
We're also continuously working with our add-on partners to keep their add-on plan offerings up-to-date and I've just shot the AirBrake guys an email. Thanks for alerting us to the problem!
I have been making Desktop applications for last few years. but now i have quite that job and thinking about doing working for myself. I have gone through many ideas. finally i decided to develop Online billing application . Since i am new in web application i know very little about web technologies.
I am thinking about developing that application in php or asp.net with mysql database. I don't know which one is better.(you can guide me here). I don't know whether its good idea or not.but i don't want to do job and work for myself that's for sure.
its going to be a big project so I was making budget for this whole project but i don't know what kind of hosting i will need for this app because database load will be very high because its billing application. i don't know how much it will cost me.I will give user free trial for 30 days to use application and if they like they can upgrade their accounts.
So i need your help to decide what kind of hosting will be appropriate.is this ok if i use webhosting that we use to host website which will cost me $10 to $15 a month or i will have to use cloud hosting which will cost me a lot?
I hope this link will give you idea. I want to make application like this : http://www.rapid-billing.com .
pls help me out. it might me small things for you but to me it matters a lot. Thanks
Initially, you won't have very high traffic, so using a cheap, shared server should be fine. If you outgrow it, then you must have some money coming in, so the added expense of cloud hosting will be more tolerable. There's no need to go all-in before you even get going.
That said, many cloud hosts offer some amount of hosting free, which would probably suit you just as well during initial development. An added plus of starting in the cloud is that you won't have to migrate later. Off the top of my head, Google App Engine and Heroku come to mind as well-known cloud hosts with a free tier. Microsoft Azure also provides a free 3 month trial, and I imagine they'd be a good host if you choose to go with ASP.
Does anyone have any idea of the average Adaptive Payments application approval time at the moment? It appears there may be a backlog as we've heard nothing from the moderators and it has been over 15 days (their usual timescale apparently). Our case is a crowdfunding website built on CodeIgniter with the Adaptive Payment gateway installed and ready to go live when we are given application approval. Our site has been active for 6months using other methods via PayPal, but it's time to move up a notch.
It depends on the permissions your application is requesting; less restricted permissions usually goes through quicker.
Even so, check with PayPal Developer Technical Services at https://www.paypal.com/dts/ if you're looking for an update.