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 revision Previous revision
Next revision
Previous revision
gateways:start [2019/08/01 18:43]
foxybrett
gateways:start [2020/03/12 20:38] (current)
marija [Card Verification and Subsequent Auth+Captures]
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 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,​ where you want to charge the customer 7 days in the future but need to make sure their card is valid first.
 +  * 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,​ 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.
 +
 +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'​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.

Site Tools