| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| primer:the_pieces [2015/06/02 03:08] – [All the Pieces: The Traditional Approach] foxybrett | primer:the_pieces [2019/01/10 05:23] (current) – [Other Gateway + Merchant Account Systems] adam |
|---|
| In order to accept credit card payments online, a merchant typically needs all of the following: | In order to accept credit card payments online, a merchant typically needs all of the following: |
| |
| * **A website.** Small websites can be static and hardcoded (like in Dreamweaver), or larger and/or dynamic and built on a CMS (Content Management System) like [[http://www.wordpress.org/|Wordpress]], [[http://www.squarespace.com/|Squarespace]], [[http://modxcms.com/|MODx]], [[http://www.expressionengine.com/|ExpressionEngine]], [[http://www.drupal.org/|Drupal]], [[http://www.joomla.org/|Joomla]], or etc. | * **A website.** Small websites can be static and hardcoded (like in Dreamweaver), or larger and/or dynamic and built on a CMS (Content Management System) like [[http://www.wordpress.org/|Wordpress]], [[http://www.squarespace.com/|Squarespace]], [[http://modxcms.com/|MODx]], [[http://www.expressionengine.com/|ExpressionEngine]], [[http://www.drupal.org/|Drupal]], [[http://www.joomla.org/|Joomla]], [[https://webflow.com/|Webflow]], etc. |
| * **An ecommerce platform.** [[http://www.foxycart.com/|FoxyCart]] is an obvious example. Nearly all ecommerce systems have an integrated CMS. FoxyCart is different in that regard. | * **An ecommerce platform.** [[http://www.foxycart.com/|FoxyCart]] is an obvious example. Nearly all ecommerce systems have an integrated CMS. FoxyCart is different in that regard. |
| * **The payment gateway.** The ecommerce system's checkout page receives payment information (ie. the credit card number) from the customer, and sends that info to the payment gateway in order to authorize transactions. The gateway responds indicating success or failure (and the corresponding error code). Most gateways have a monthly fee as well as a small (~$0.05 USD) per transaction fee. Gateways typically send transactions to your merchant account to capture once a day as a "batch". Common gateways are Authorize.net, Stripe, Braintree, and Chase Paymentech. | * **The payment gateway.** The ecommerce system's checkout page receives payment information (ie. the credit card number) from the customer, and sends that info to the payment gateway in order to authorize transactions. The gateway responds indicating success or failure (and the corresponding error code). Most gateways have a monthly fee as well as a small (~$0.05 USD) per transaction fee. Gateways typically send transactions to your merchant account to capture once a day as a "batch". Common gateways are Authorize.net, Stripe, Braintree, and Chase Paymentech. |
| |
| * [[http://www.paypal.com/|PayPal Payments Pro]] rolls together the gateway and merchant account quite effectively, and could also be considered a "bank account" (though it is important to note that it is not necessarily regulated like a bank account). In addition, PayPal offers some basic cart and checkout functionality, which makes it somewhat of an "ecommerce platform". | * [[http://www.paypal.com/|PayPal Payments Pro]] rolls together the gateway and merchant account quite effectively, and could also be considered a "bank account" (though it is important to note that it is not necessarily regulated like a bank account). In addition, PayPal offers some basic cart and checkout functionality, which makes it somewhat of an "ecommerce platform". |
| * [[http://checkout.google.com/|Google Checkout]] and [[http://2co.com/|2Checkout]] offer limited cart, gateway, and merchant account functionality as well. (Please note that neither GCo nor 2Co are currently supported by FoxyCart.) | * [[http://2co.com/|2Checkout]] offer limited cart, gateway, and merchant account functionality as well. |
| |
| ===== Ecommerce Platform + Merchant Accounts or Gateways ===== | ===== Ecommerce Platform + Merchant Accounts or Gateways ===== |
