Documentation You are here: start » gateways

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
gateways:start [2019/12/11 00:32] – [Authorization and Capture: How the Money Flows] foxybrettgateways: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 === +==== 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...+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, where you want to charge the customer 7 days in the future but need to make sure their card is valid first.   * Free trials on a subscription, where you want to charge the customer 7 days in the future but need to make sure their card is valid first.
Line 87: Line 87:
 There are some downsides, though: There are some downsides, though:
  
-  * You need to manually capture every verified transaction manually (or build an API integration, which is definitely the better approach if you have any sort of volume).+  * If you've selected //Enabled, always and only verify//, you need to capture every verified transaction manually (or build an API integration, which is definitely the better approach if you have any sort of volume). Otherwise, it will verify only $0 transactions (for example, where the transaction has future subscription start dates and are not charged on the first transaction date).
   * Just because a card verified doesn't mean it'll work for the full amount, so you'll need to also build robust procedures or automated handling of errors.   * Just because a card verified doesn't mean it'll work for the full amount, so you'll need to also build robust procedures or automated handling of errors.
  
 This approach is generally only recommended for advanced users who have very, very specific workflows. 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: Will perform a verification on zero-amount transactions when a payment method is required (such as future subscriptions). Non zero-amount transactions will be authorized or auth+captured at the full amount.
 +  * Always and only verify: For all transactions where a payment method is required (both zero-amount and non zero-amount), the payment method will be verified. Payment will not be collected without additional action. Only recommended in specific situations.
 + 
 +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're typically easy to understand once you know what you're looking for. Please read our [[:primer:errors|primer on payment processing errors]], because knowing is half the battle. Payment errors are a fact of e-commerce life, but fear not: They're typically easy to understand once you know what you're looking for. Please read our [[:primer:errors|primer on payment processing errors]], because knowing is half the battle.

Page Tools

Site Tools