Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
gateways:start [2017/05/02 18:48] – [Authorization and Capture: How the Money Flows] foxybrett | gateways:start [2020/03/12 20:38] – [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¢/ | + | 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) |
</ | </ | ||
Line 11: | Line 11: | ||
===== Supported Gateways & Other Payment Methods ===== | ===== Supported Gateways & Other Payment Methods ===== | ||
- | {| 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 30: | Line 38: | ||
filter | filter | ||
---- | ---- | ||
- | |} | ||
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, | (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, | ||
- | 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. | ||
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, | ||
+ | * 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. | ||
==== 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' |