|This article is of interest to the following WikiProjects:|
|This article was nominated for merging with Payment service provider on March 8, 2007. The result of the discussion was Not merge.|
- 1 SSL Certificates are independent of payment gateways
- 2 What Exactly Do They Do?
- 3 Only for e commerce?
- 4 Unabbreviated ASP
- 5 Scrape account
- 6 Popular Payment Gateways Section
- 7 Added Trasaction processing workflow diagram with Payment Gateway
- 8 List of providers
- 9 Difference between a Payment Gateway and a PSP
- 10 Charges to Payment Gateway
- 11 digitalbusiness.gov.au Sources Need Updating
SSL Certificates are independent of payment gateways
They work by providing a secure connection between the website and the payment gateway.
Depending on the payment gateway a website may not need a SSL. Using an API integration method, a website's visitor remains on the website through the entire transaction process, and a SSL is required. Using a simple method that some gateways provide, a visitor is redirected to the payment gateway to complete a transaction, where the SSL is handled by the Payment Gateway. The API method is more expensive because of the required SSL, but it provides a better user experience and if usually a better system for most websites. --Jestep 15:15, 30 August 2006 (UTC)
What Exactly Do They Do?
Why do payment gateways exist? What prevents merchants from communicating directly with aquiring banks? How do Bank neutral payment gateways operate, for example, who does authorize.net communicate with? Do they talk to every single bank in the country, or is there some network that they hook in to.. and if it is the latter why do I need them instead of doing it myself? --188.8.131.52 23:59, 30 August 2006 (UTC)
Basically, the payment gateways are a secure connection to the processing networks. As far as processing networks go, they are very complex networks that connect directly to the back-end processors and they also connect to the card issuing banks. The processors have a series of platforms under them that the payment gateways connect to. Here is a really simple article and diagram to help understand processing platforms Processing Platforms.
Now as far as why you cant connect directly to the processor and process through them. There are several reasons. First off, they flat out don't allow it. The processors in no way want to deal with millions of customers trying to connect servers directly to them to process credit cards. Apart from being a technical support nightmare, there are so many ways that servers could connect to them, that it is just way more than they want to deal with. By using payment gateways, they know exactly what data is going to them which is great for control and fraud screening. Secondly, some ecommerce sites do connect directly to them, but these would be the ones doing hundreds of millions per year in processing. These companies and payment gateways have to pay enormous setup and yearly fees to get approved to send the processor transactions. I've heard that it costs something like $100,000 and $50,000 per year to have a payment gateway or a company approved on a single processing platform. So basically based on the sheer price and the amount of effort it would require to send transactions directly to a processor, it just cant be worth it for anything but a payment gateway or a huge ecommerce site. --Jestep 16:46, 4 September 2006 (UTC)
Only for e commerce?
I disagree with two aspects of this article: 1. A Payment Gateway is only for ecommerce. There are many companies who provide connectivity from a "Physical" Point of Sale devices to the various Processors.
2. A Payment Gateway is the equivalent of a Point of Sale; it is the equivalent of a credit card terminal. A Shopping cart would be the equivalent of a Point of Sale.
Does anyone know of the server and gateway requirements for these aspects of payment gateways?
• Payments methods • Transaction logging • Cost • Licence details • Vendor and product reputation • Compatibility with client system • Installation and configuration methods
- Not true, a Payment Gateway is not equivilent to a credit card terminal. A gateway might be as simple as a "pass-through" to a particular payment processor, or may add additional value added services, or unique protocols that allow multiple payment options to point-of-sale, or shopping cart systems not available in any credit card terminal device.
I changed asp to application service provider so people don't confuse it with Active Server Pages. Ryratt 20:07, 14 May 2007 (UTC)
What's a scrape account? I couldn't find a definition of this anywhere.
Otherwise very informative.
Popular Payment Gateways Section
I removed the smaller players and left the most popular ones for reference. This is to curb the continual addition of providers as an advertisement. At the rate we were going it would have been a massive list which is not the point of this article. I left a comment in the page to let editors know not to add any more. If anyone disagrees with this please post here. stymiee 13:57, 18 July 2007 (UTC)
I believe some of the 'payment gateway's listed are poorly written articles such as Authorize.Net which has been marked as an advertisements or Cybersource (not a single reference). I added appropriate references to the see also that further explain online payments and other works that explain large players in online payments. --Jjimagery (talk) 05:51, 4 March 2010 (UTC)
- Authorize.Net is by far the largest and most recognizable payment gateway and thus the best example of one so I returned its link. If you don't like the article improve it. That's how Wikipedia works. eWay is a relative unknown so I removed it. Also, we don't want to turn that page into a listing of payment gateways on Wikipedia. They have special pages for that. I left cybersource off since they just own Authorize.Net and thus were redundant. stymiee (talk) 12:59, 4 March 2010 (UTC)
- Authorize.Net may be known in the United States, however eWAY is large global payment gateway, ask anyone in Australia or New Zealand and they will tell you eWAY, it is also growing at a very large rate in the UK market. --Jjimagery (talk) 22:07, 4 March 2010 (UTC)
- Eway is not a payment gateway as defined in this article. A payment gateway does not process credit cards themselves. They act as a middle man between a website or software and a merchant account provider. This is how it works in the US but not in Austrailia or New Zealand or the rest of the world. They fall under Payment Service Provider . You can try to place your link there. —Preceding unsigned comment added by Stymiee (talk • contribs) 12:51, 5 March 2010 (UTC)
Added Trasaction processing workflow diagram with Payment Gateway
List of providers
I noticed a list of payment gateways at http://drupal.org/node/66299 and expected to find a more complete list here, but I didn't notice any. Perhaps someone would be willing to start one? Jasonkhanlar (talk) 03:10, 10 October 2009 (UTC)
Difference between a Payment Gateway and a PSP
- In my line of work (IT specializing on online payments), we use Payment Gateway from a Payment card industry perspective, e.g. more traditional credit card gateways. Payment service providers tend to be more broad: including completely different payment methods such as wallets, direct debits or online banking and offering more features. Aardbeitje (talk) 19:56, 31 May 2013 (UTC)
Charges to Payment Gateway
How many kind of charges would be applied to Payment Gateway (like issuing bank charges..etc.) in end-to-end online transaction processing? It would be value basis or count basis charges? — Preceding unsigned comment added by 184.108.40.206 (talk) 07:31, 1 June 2012 (UTC)
digitalbusiness.gov.au Sources Need Updating
Some of the sources from www.digitalbusiness.gov.au are now broken links following a website upgrade. The content has changed but the original content should be available on the Wayback machine on archive.org. I'm not sure of wikipedia's policy or what the differences are - could someone check what needs to be done.
For reference the new pages are: