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 [2020/01/10 20:35]
marija [Supported Gateways & Other Payment Methods]
gateways:start [2020/03/12 20:38] (current)
marija [Card Verification and Subsequent Auth+Captures]
Line 12: Line 12:
 ===== Supported Gateways & Other Payment Methods ===== ===== Supported Gateways & Other Payment Methods =====
 ---- datatable gateways ---- ---- datatable gateways ----
-cols    : name, %pageid%+cols    : name, %pageid%, supports-3dsecure
 headers : Gateway Name, Link headers : Gateway Name, Link
 max     : 200 max     : 200
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.
  

Site Tools