Use the values in the tables below to configure the Affirm payment provider/authorizer with the described settings.




(The procedures for accessing and configuring these settings are described in Add an Authorizer.)

Parameter

Value

Comments

AUTHORIZER NAME

Affirm

Can be any meaningful value.

AUTHORIZER CODE

Affirm

This value should exactly match the provider/ authorizerBean implementation. 
(Service Implementation Bean is a term used in Java Platform, Enterprise Edition, for a Java object implementing a Web service.)
 
Do not change if you are not sure.

SITE URL

Test

Production

.

https://sandbox.affirm.com/api/v2/

https://api.affirm.com/api/v2/

The field must be populated, but the value is not currently used. Any value is valid.
Suggest using specified values for consistency/clarity.

LOGIN URL


Not used

REPORTS URL
Not used

CUSTOM URL 1

 https://cdn-assets.affirm.com/images/buttons/checkout/60x296-blue.jpg

Used for the Agile Summary Page 'Checkout with Affirm' Button

START DATE

10/20/08 

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

STATUS

Active 

Should be "Active" for the current provider.
(Status of "New" is not recommended)



(The procedures for accessing and configuring these settings are described in Add Authorization Info.)

Parameter

Value

Comments

AUTHORIZER NAME

Affirm

Match the value in the Authorizer Name field in the Authorizer parameters.

AUTHORIZATION
INFO CODE

Affirm

Match the value in the Authorizer Code field in the Authorizer parameters.

USER NAME


Not used

PASSWORD


Not used

EXTERNAL MERCHANT ID

 

Not used

TERMINALID

 

Not used

PAYMENTECH BIN

 

Not used

PAYMENT TOKENIZATION
ENABLED


Not used

DOES AUTHORIZER SUPPORT
MULTIPLE CAPTURE AGAINST
SINGLE AUTHORIZATION?

No 

Does not support multiple captures against a single authorization.
Must be "No"

START DATE

11/17/15 

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

CURRENCIES

USD (United States Dollar)

Select from list of available currencies, as applicable.

ITEM TYPES
Applicable for 6i15.5.0 only.(Optional)
 PAYMENT TYPES3rd Party Checkout

DISABLE FRAUD DETECTION
FOR ORDER SOURCES


Not used

STATUS

Active

Should be "Active" for the current provider.
(Status of "New" is not recommended)



(The procedures for accessing and configuring these settings are described in Configure Authorization Info Parameters.)

Parameter

Default Value

Comments

AffirmJsUrl

Test:

Production:

.

https://cdn1-sandbox.affirm.com/js/v2/affirm.js

https://cdn1.affirm.com/js/v2/affirm.js


Used to load Affirm JavaScript.

PublicApiKey

Test:

Production:


Varies by merchant

For Test:
Retrieve the Public API key via the Affirm dashboard at:

https://sandbox.affirm.com/dashboard/#/apikeys

For Production:
Retrieve the Public API key via the Affirm dashboard at:
https://www.affirm.com/dashboard/#/apikeys

PrivateApiKey

Test:

Production:


Varies by merchant

For Test:
Retrieve the Private API key via the Affirm dashboard at:
https://sandbox.affirm.com/dashboard/#/apikeys

For Production:
Retrieve the Private API key via the Affirm dashboard at:
https://www.affirm.com/dashboard/#/apikeys

 DoNotProcessTransaction No Optional parameter.

For payment transactions that are for reporting purposes only. When "Yes," third parties that manage their own payments can send full transaction details upon order import so that EDGE can track the payments in an Order Details page or Payment Transactions report without actually processing any payments.

Valid values:

  • Yes - a payment transaction WILL NOT be processed
  • No (default value) - a payment transaction WILL be processed