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
Next revisionBoth sides next revision
gateways:start [2019/12/11 00:32] – [Authorization and Capture: How the Money Flows] foxybrettgateways:start [2020/03/12 18:16] – [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 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...
  
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 manually 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.
  

Page Tools

Site Tools