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 [2019/08/01 18:33] – [Supported Gateways & Other Payment Methods] foxybrett | gateways:start [2020/03/12 18:16] – [Card Verification and Subsequent Auth+Captures] marija | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== Supported Gateways & Other Payment Methods ===== | ===== Supported Gateways & Other Payment Methods ===== | ||
| - | {| class=" | ||
| - | |- | ||
| - | | style=" | ||
| ---- datatable gateways ---- | ---- datatable gateways ---- | ||
| cols : name, %pageid%, supports-3dsecure | cols : name, %pageid%, supports-3dsecure | ||
| 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> | + | |
| + | 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 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 manually 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' | ||