Page tree
Skip to end of metadata
Go to start of metadata

The table below shows a summary of the features supported in EDGE by each of the payment services providers/authorizers. 

Payment Services Providers Supported Features

      Y = Yes (supported), N = No (not supported), N/A = Not applicable for this payment services provider/authorizer


Features

AdyenAffirmAmazon PayApple Pay via CyberSource

Authorize.NET

Clutch

CyberSource

Element

Mercury

 PaymentechPayPalPayPal via CyberSourceShift4TrustCommerce

Vantiv
(formerly Litle)

Default

Supported Payment Types

  • Credit Card
  • Gift Card
  • eCheck



Y
N
N



N/A
N/A
N/A



N/A
N/A
N/A



Y
N/A
N/A



Y
N
N



N
Y
N



Y
N
Y




N
N



N
Y
N




N
Y



N/A
N/A
N/A



N/A
N/A
N/A



Y
Y
N




N
N



Y
N
N


(See note)
N/A
N/A
N/A

Gift Card Activation Type

  • Preloaded
  • Online


N/A
N/A



N/A
N/A



N/A
N/A



N/A
N/A



N/A
N/A



Y
Y



N/A
N/A



N/A
N/A




N



N/A
N/A



N/A
N/A



N/A
N/A



Y
N



N/A
N/A



N/A
N/A 



N/A
N/A
Supports Payment TokenizationYYYYYNY YY Y NN
Supports Autoship TokenizationYNNN Y Y NNN
Supports Multi Capture Against Single AuthorizationYNNN Y NN/A YY YN
Supports Multiple CurrenciesYNYY Y Y NYY
SDK &/or API VersionSDK/1.8.0API/v2SDK/3.3.4SOAP/1.137

SDK/1.8.8

SOAP/v4

SOAP/1.137

SOAP 

SOAP

SOAP/2.7

SOAP/124.0

SOAP/1.137

HTTP/1.9

SDK/4.2.0 

SDK/8.31.1

N/A

Notes:

  • In data security, "Payment Tokenization" is the process of substituting a sensitive data element with a non-sensitive equivalent (a token) that has no extrinsic or exploitable meaning or value. The token is a reference that maps back to the sensitive data through a tokenization system.
    .
  • Beginning in EDGE 16.0., "Autoship Tokenization" support is provided for specified payment services providers. (A merchant using EDGE 6i.15.5 or older cannot use autoship if they use payment tokenization.)
    Autoship tokenization means that when a customer's credit card information is tokenized (as described above in "Payment Tokenization"), the token, rather than the actual credit card information, can be retained and submitted as payment for recurring order shipments.
    .
  • If the payment provider/authorizer does not support multiple captures against a single authorization, EDGE captures the amount for the shipment and creates a new authorization for the remaining balance. When this is the case, either the payment must be tokenized or a credit card and/or gift card number must be part of the order. (This is not applicable for the Affirm payment provider/authorizer.)
    .

  • EDGE does not currently support true tokenization. This means that a token cannot be associated with an EDGE member for any future order. (However, payment details can be saved for an EDGE member via EDGE or an Agile front end using encryption.)
    .
  • The "Default" authorizer is used only for non-processing payment types – those that are not subject to authorization by a payment services provider. Non-processing payment types include:
    • Purchase Order Number
    • Checking (for CyberSource ONLY, Checking is supported as a standard processing payment type, subject to authorization)
    • Gift Certificate 
    • Bill Me
    • Member Budget
    • COD
    • Cash
    • Budget Center
    • Charges Waived

To continue . . .

Before you begin configuring EDGE for any of the supported payment providers/authorizers, you need to obtain certain information from the provider, as described in Before You Begin...

.



  • No labels