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 revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
gateways:start [2017/07/26 01:49] – [Supported Gateways & Other Payment Methods] adamgateways:start [2020/03/12 18:16] – [Card Verification and Subsequent Auth+Captures] marija
Line 2: Line 2:
 <WRAP tip round 60%> <WRAP tip round 60%>
 //**Need a gateway?**// //**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.+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% (as low as 2.7% depending on your sales volume) + 30¢/transaction with no monthly, setup, or contract.
 </WRAP> </WRAP>
  
Line 11: Line 11:
  
 ===== Supported Gateways & Other Payment Methods ===== ===== Supported Gateways & Other Payment Methods =====
-{| class="clouds" 
-|- 
-| style="width:57%; padding-right:3%" | 
 ---- datatable gateways ---- ---- datatable gateways ----
-cols    : name, %pageid%+cols    : name, %pageid%, supports-3dsecure
 headers : Gateway Name, Link headers : Gateway Name, Link
 max     : 200 max     : 200
Line 21: Line 18:
 sort    : %pageid% sort    : %pageid%
 ---- ----
-| + 
-//**Filter Gateways by Supported Country**// +==== Filter Gateways by 3D Secure Support ==== 
-\\ 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''.+ 
 +Click below to see which gateways support 3D Secure. 
 +---- datacloud ---- 
 +field : supports-3dsecure 
 +min : 1 
 +limit : 300 
 +filter  : type=gateway 
 +---- 
 + 
 +==== 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 ---- ---- datacloud ----
 field : countries field : countries
Line 30: Line 38:
 filter  : type=gateway filter  : type=gateway
 ---- ----
-|} 
  
  
Line 62: Line 69:
 (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.) (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).
  
 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.
Line 71: Line 78:
 In most situations we strongly recommend doing an auth+capture. If you do have specific requirements that necessitate auth-only processing we encourage you to test thoroughly and keep up to date on any changes your gateway may make that impact that functionality. In most situations we strongly recommend doing an auth+capture. If you do have specific requirements that necessitate auth-only processing we encourage you to test thoroughly and keep up to date on any changes your gateway may make that impact that functionality.
  
 +==== Card Verification and Subsequent Auth+Captures ====
 +Foxy support (for some gateways) the ability to verify a card with a $0 or $1 auth. (Check with your processor for the correct value to use. If you pass the wrong value, you can be hit with a small authorization misuse fee, or it can just error.) Verifications are useful for situations like...
 +
 +  * Free trials on a subscription, where you want to charge the customer 7 days in the future but need to make sure their card is valid first.
 +  * Pre-orders. (This is a bigger topic, but it's a valid use case.)
 +  * Accepting transactions where you might need to adjust the final charge //upwards// (ie. charge //more// than was displayed to the customer on the checkout).
 +
 +There are some downsides, though:
 +
 +  * If you've selected //Enabled, always and only verify//, you need to manually capture every verified transaction manually (or build an API integration, which is definitely the better approach if you have any sort of volume). Otherwise, it will verify only $0 transactions (for example, where the transaction has future subscription start dates and are not charged on the first transaction date).
 +  * Just because a card verified doesn't mean it'll work for the full amount, so you'll need to also build robust procedures or automated handling of errors.
  
 +This approach is generally only recommended for advanced users who have very, very specific workflows.
 ==== Gateway Errors and What To Do About Them ==== ==== Gateway Errors and What To Do About Them ====
 Payment errors are a fact of e-commerce life, but fear not: They're typically easy to understand once you know what you're looking for. Please read our [[:primer:errors|primer on payment processing errors]], because knowing is half the battle. Payment errors are a fact of e-commerce life, but fear not: They're typically easy to understand once you know what you're looking for. Please read our [[:primer:errors|primer on payment processing errors]], because knowing is half the battle.

Page Tools

Site Tools