no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revisionNext revision | |||
— | gateways:start [2012/06/26 20:55] – fixing cache clearing link foxybrett | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOCACHE~~ | ||
+ | ====== Payment Gateways: Notes and Information ====== | ||
+ | <WRAP important round 60%> | ||
+ | //**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.</ | ||
+ | |||
+ | ===== What you NEED to KNOW ===== | ||
+ | ==== Gateways, Merchant Accounts, Bank Accounts, Oh My! ==== | ||
+ | Accepting credit card payments online is more difficult than it seems it should be, and matters are complicated by new and evolving systems that not only combine previously distinct aspects but also are redefining the payment process and creating entirely new options. If you aren't already intimately familiar with how the myriad pieces of e-commerce interact [[: | ||
+ | |||
+ | ==== CSC (CID, CVV2, etc.) Support, Requirements, | ||
+ | Some FoxyCart functionality may require or allow a transaction to be processed //without// a Card Security Code (the " | ||
+ | * [[: | ||
+ | * [[: | ||
+ | * Returning customers using previously saved payment info | ||
+ | |||
+ | If you're using this functionality we strongly recommend turning off the CSC requirements in your gateway' | ||
+ | |||
+ | Also, please note that the CSC is not allowed to be stored, per [[https:// | ||
+ | |||
+ | Gateways that may require additional steps or features in order to process transactions without a CSC include: | ||
+ | * [[.: | ||
+ | |||
+ | ==== TESTING v. LIVE, Gateway Settings and Accounts ==== | ||
+ | Almost every gateway provider also provides their customers with test accounts (also called development accounts or sandbox accounts) //for use on the gateway' | ||
+ | |||
+ | To make testing easier for FoxyCart users, FoxyCart provides the ability to enter your own test account information with which to test. What is critical to understand is that, in almost all cases, **a live account will //not// work on if the test gateway is selected in FoxyCart**. FoxyCart will send the transaction to entirely separate systems based on your store' | ||
+ | |||
+ | |||
+ | ==== Authorization and Capture: How the Money Flows ==== | ||
+ | An important but often misunderstood piece of credit card processing is the relationship between " | ||
+ | |||
+ | (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.) | ||
+ | |||
+ | The other, much more common way to process transactions is to do the authorization and capture at the same time, referred to as an " | ||
+ | |||
+ | 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 " | ||
+ | * Authorizations don't last forever. 3 days is probably as far as you'd want to go under normal circumstances, | ||
+ | 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:// | ||
+ | |||
+ | 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. | ||
+ | |||
+ | |||
+ | ==== Gateway Errors and What To Do About Them ==== | ||
+ | Payment errors are a fact of e-commerce life, but fear not: They' | ||
+ | |||
+ | |||
+ | ==== Requesting New Gateway Support ==== | ||
+ | Please [[http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Supported Gateways & Other Payment Methods ===== | ||
+ | <WRAP tip round> | ||
+ | There should be a list of FoxyCart-supported gateways below. If there' | ||
+ | </ | ||
+ | |||
+ | {| class=" | ||
+ | |- | ||
+ | | style=" | ||
+ | ---- datatable gateways ---- | ||
+ | cols : name, %pageid% | ||
+ | headers : Gateway Name, Link | ||
+ | max : 100 | ||
+ | filter | ||
+ | sort : %pageid% | ||
+ | ---- | ||
+ | | | ||
+ | //**Filter Gateways by Supported Country**// | ||
+ | \\ Country codes below are according to [[wp> | ||
+ | ---- datacloud ---- | ||
+ | field : countries | ||
+ | min : 1 | ||
+ | limit : 300 | ||
+ | filter | ||
+ | ---- | ||
+ | |} |