Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
gateways:start [2019/08/01 18:43] – foxybrett | gateways:start [2021/05/28 21:31] (current) – [Card Verification and Subsequent Auth+Captures] marija | ||
---|---|---|---|
Line 78: | 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 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' |