Documentation You are here: start » gateways

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
gateways:start [2012/06/26 20:55]
foxybrett fixing cache clearing link
gateways:start [2017/05/02 18:48] (current)
foxybrett [Authorization and Capture: How the Money Flows]
Line 1: Line 1:
-~~NOCACHE~~ 
- 
 ====== Payment Gateways: Notes and Information ====== ====== Payment Gateways: Notes and Information ======
-<​WRAP ​important ​round 60%>+<​WRAP ​tip round 60%> 
 +//**Need a gateway?​**//​ 
 +We've partnered with a company we trust to serve US merchants. Please [[hello@foxycart.com|contact us]] and we'll connect you. The plans are 2.9% + 30¢/​transaction with no monthly, setup, or contract. There'​s also a 2.2% + 25¢ plan as well. 
 +</​WRAP>​ 
 + 
 +<WRAP info round 60%>
 //**Know Your Money Flow!**// //**Know Your Money Flow!**//
 Please read at least the first "Need to Know" section of this page prior to using FoxyCart on a live e-commerce site. Not everything with e-commerce, gateways, merchant account, and payment information is immediately obvious or well known. Really, trust us. We see stores lose sales //all the time// for various reasons.</​WRAP>​ Please read at least the first "Need to Know" section of this page prior to using FoxyCart on a live e-commerce site. Not everything with e-commerce, gateways, merchant account, and payment information is immediately obvious or well known. Really, trust us. We see stores lose sales //all the time// for various reasons.</​WRAP>​
 +
 +
 +===== Supported Gateways & Other Payment Methods =====
 +{| class="​clouds"​
 +|-
 +| style="​width:​57%;​ padding-right:​3%"​ |
 +---- datatable gateways ----
 +cols    : name, %pageid%
 +headers : Gateway Name, Link
 +max     : 100
 +filter ​ : type=gateway
 +sort    : %pageid%
 +----
 +|
 +//**Filter Gateways by Supported Country**//
 +\\ Country codes below are according to [[wp>​ISO_3166-1_alpha-2|ISO 3166-1 alpha-2]]. <wrap tip>''​GB''​ is the ''​UK''</​wrap>,​ and Greece is ''​GR''​ and not ''​IL''​.
 +---- datacloud ----
 +field : countries
 +min : 1
 +limit : 300
 +filter ​ : type=gateway
 +----
 +|}
 +
 +
  
 ===== What you NEED to KNOW ===== ===== What you NEED to KNOW =====
Line 32: Line 60:
 An important but often misunderstood piece of credit card processing is the relationship between "​authorization"​ and "​capture"​. The easiest way to explain it is by using a gas station as an example. You drive up to the pump and insert your credit card, at which point the card is "​authorized"​ for (let's say) $75. This authorization checks with your bank to make sure you have the funds, just like a normal transaction,​ but //​doesn'​t yet charge the card// ("​capture the funds"​),​ since the final dollar amount is unknown. Once you have finished pumping and the final transaction amount is known (say, $45.03), the system issues a "​capture"​ for $45.03. The first part is an "​authorization only", or "​auth-only",​ transaction. The second part is the capture. An important but often misunderstood piece of credit card processing is the relationship between "​authorization"​ and "​capture"​. The easiest way to explain it is by using a gas station as an example. You drive up to the pump and insert your credit card, at which point the card is "​authorized"​ for (let's say) $75. This authorization checks with your bank to make sure you have the funds, just like a normal transaction,​ but //​doesn'​t yet charge the card// ("​capture the funds"​),​ since the final dollar amount is unknown. Once you have finished pumping and the final transaction amount is known (say, $45.03), the system issues a "​capture"​ for $45.03. The first part is an "​authorization only", or "​auth-only",​ transaction. The second part is the capture.
  
-(Another option would be for the gas station to authorize a small amount like $1 just to make sure that it's a valid card, then upon completion clear that auth and issue an auth+capture for the full amount in one go.)+(Another option would be for the gas station ​(or any merchant) ​to authorize a small amount like $1 just to make sure that it's a valid card, then upon completion clear that auth and issue an auth+capture for the full amount in one go. That approach can be sub-optimal,​ though, as a $1 charge might go through fine, but a $75 charge might fail for insufficient funds. This approach also requires storing payment information in one way or another, which can lead to its own challenges.)
  
 The other, much more common way to process transactions is to do the authorization and capture at the same time, referred to as an "​auth/​capture"​ or "​auth/​capture"​. Imagine buying groceries: You go to checkout, the total charge is determined, and your card is charged (both auth'd and captured at the same time). The other, much more common way to process transactions is to do the authorization and capture at the same time, referred to as an "​auth/​capture"​ or "​auth/​capture"​. Imagine buying groceries: You go to checkout, the total charge is determined, and your card is charged (both auth'd and captured at the same time).
Line 38: Line 66:
 Where things get confusing is on the proper usages of an auth-only transaction. It is often thought of as a way to accept pre-orders or to handle trial billing periods. While you //could// use an auth-only to handle these types of charges, it might not be a great idea for a few reasons. Where things get confusing is on the proper usages of an auth-only transaction. It is often thought of as a way to accept pre-orders or to handle trial billing periods. While you //could// use an auth-only to handle these types of charges, it might not be a great idea for a few reasons.
   * Authorizations effectively "​hold"​ the amount authorized. So if you auth $300, that $300 is unavailable to the customer even if you haven'​t captured the funds. (If you don't capture and the auth expires, the funds will be released back to the customer, but in the meantime they may have overdrafted their account.)   * Authorizations effectively "​hold"​ the amount authorized. So if you auth $300, that $300 is unavailable to the customer even if you haven'​t captured the funds. (If you don't capture and the auth expires, the funds will be released back to the customer, but in the meantime they may have overdrafted their account.)
-  * Authorizations don't last forever. 3 days is probably as far as you'd want to go under normal circumstances,​ and 30 days appears to be the upper limit, though the exact details will depend on your gateway, and perhaps ​variety ​of other factors.+  * Authorizations don't last forever. 3 days is probably as far as you'd want to go under normal circumstances,​ and 30 days appears to be the upper limit, though the exact details will depend on a number ​of factors, including the card type (Visa, MasterCard, AmEx, etc.).
 A better use of auth-only transactions would be to handle expected variations in product delivery or final charges. For example, if your shipping charges vary by factors that FoxyCart cannot account for, or products may not be available regularly, you may want to auth-only then adjust the final transaction amount before capturing the funds. Important to note, however, is that you can never capture //more// than you've initially authorized when using a traditional gateway. Some gateways allow you to capture only as much as has been authorized, while others (([[https://​cms.paypal.com/​us/​cgi-bin/?​cmd=_render-content&​content_ID=developer/​howto_admin_authcapture|PayPal]]'​s authorization & capture functionality)) may allow you to capture up to a certain percentage of the authorized amount, but not more than a certain dollar amount higher. A better use of auth-only transactions would be to handle expected variations in product delivery or final charges. For example, if your shipping charges vary by factors that FoxyCart cannot account for, or products may not be available regularly, you may want to auth-only then adjust the final transaction amount before capturing the funds. Important to note, however, is that you can never capture //more// than you've initially authorized when using a traditional gateway. Some gateways allow you to capture only as much as has been authorized, while others (([[https://​cms.paypal.com/​us/​cgi-bin/?​cmd=_render-content&​content_ID=developer/​howto_admin_authcapture|PayPal]]'​s authorization & capture functionality)) may allow you to capture up to a certain percentage of the authorized amount, but not more than a certain dollar amount higher.
  
Line 55: Line 83:
  
  
-===== Supported Gateways & Other Payment Methods ===== 
-<WRAP tip round> 
-There should be a list of FoxyCart-supported gateways below. If there'​s not, then something went wrong on our wiki and you should [[http://​wiki.foxycart.com/​gateways/​start?​purge=true|click here]] to reload this page.  Sorry for any inconvenience! We found a bug and we're working on a fix. 
-</​WRAP>​ 
- 
-{| class="​clouds"​ 
-|- 
-| style="​width:​57%;​ padding-right:​3%"​ | 
----- datatable gateways ---- 
-cols    : name, %pageid% 
-headers : Gateway Name, Link 
-max     : 100 
-filter ​ : type=gateway 
-sort    : %pageid% 
----- 
-| 
-//**Filter Gateways by Supported Country**// 
-\\ Country codes below are according to [[wp>​ISO_3166-1_alpha-2|ISO 3166-1 alpha-2]]. <wrap tip>''​GB''​ is the ''​UK''</​wrap>,​ and Greece is ''​GR''​ and not ''​IL''​. 
----- datacloud ---- 
-field : countries 
-min : 1 
-limit : 300 
-filter ​ : type=gateway 
----- 
-|} 

Site Tools