Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
gateways:start [2012/08/02 02:27] – foxyfred | gateways:start [2021/05/28 21:31] (current) – [Card Verification and Subsequent Auth+Captures] marija | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Payment Gateways: Notes and Information ====== | ====== Payment Gateways: Notes and Information ====== | ||
- | < | + | < |
+ | //**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% (as low as 2.7% depending on your sales volume) + 30¢/ | ||
+ | </ | ||
+ | |||
+ | <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.</ | 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.</ | ||
Line 6: | Line 11: | ||
===== Supported Gateways & Other Payment Methods ===== | ===== Supported Gateways & Other Payment Methods ===== | ||
- | <WRAP tip round> | ||
- | There should be a list of FoxyCart-supported gateways below. If there' | ||
- | </ | ||
- | |||
- | {| class=" | ||
- | |- | ||
- | | style=" | ||
---- datatable gateways ---- | ---- datatable gateways ---- | ||
- | cols : name, %pageid% | + | cols : name, %pageid%, supports-3dsecure |
headers : Gateway Name, Link | headers : Gateway Name, Link | ||
- | max : | + | max : |
filter | filter | ||
sort : %pageid% | sort : %pageid% | ||
---- | ---- | ||
- | | | + | |
- | //**Filter Gateways by Supported Country**// | + | ==== Filter Gateways by 3D Secure Support ==== |
- | \\ Country codes below are according to [[wp> | + | |
+ | Click below to see which gateways support 3D Secure. | ||
+ | ---- datacloud ---- | ||
+ | field : supports-3dsecure | ||
+ | min : 1 | ||
+ | limit : 300 | ||
+ | filter | ||
+ | ---- | ||
+ | |||
+ | ==== Filter Gateways by Supported Country | ||
+ | |||
+ | Country codes below are according to [[wp> | ||
---- datacloud ---- | ---- datacloud ---- | ||
field : countries | field : countries | ||
Line 29: | Line 38: | ||
filter | filter | ||
---- | ---- | ||
- | |} | ||
Line 59: | Line 67: | ||
An important but often misunderstood piece of credit card processing is the relationship between " | 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.) | + | (Another option would be for the gas station |
- | 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" | + | 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" |
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 " | * Authorizations effectively " | ||
- | * Authorizations don't last forever. 3 days is probably as far as you'd want to go under normal circumstances, | + | * 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:// | 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. | 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 supports (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, | ||
+ | * 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 capture every verified transaction manually (or build an API integration, | ||
+ | * Just because a card verified doesn' | ||
+ | |||
+ | This approach is generally only recommended for advanced users who have very, very specific workflows. | ||
+ | |||
+ | =====Settings Summary===== | ||
+ | Here is a summary of the verification settings: | ||
+ | * Disabled: Will never verify payment methods. Not recommended. | ||
+ | * Enabled, automatically: | ||
+ | * Always and only verify: For all transactions where a payment method is required (both zero-amount and non zero-amount), | ||
+ | |||
+ | In all cases, a payment method will not be required for “free” transactions (assuming there is not a subscription present), such as if a coupon brings the order total to zero. | ||
==== 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' | Payment errors are a fact of e-commerce life, but fear not: They' |