Authorize.net Quick Setup is only one of Pepperi's Quick Setup connectors, allowing you to simply integrate to external systems using a quick setup configuration interface in the back office.

Authorize.net Quick Setup quickly integrates Pepperi with authorize.net payment provider.

• Customers can easily pay for orders using their credit card via Authorize.net
• Customers' payment method can be authorized only for later payment
• Customers' payment method can be saved for next purchase (optional)
• Prevents duplicate payments by tracking all payments within Pepperi
• Easy setup by Pepperi Admin in the Quick Setup
• View all Pepperi payment statuses in your Authorize.net business account

Authorize.net quick setup configuration allows you to set up the connection to your authorize.ent merchant account, and setup the workflow you require.

You can create multiple configurations for use by different Pepperi transactions.

Examples of different types of requirements that may be configured in the quick setup:

• Buyers payment is both authorized and captured for payment, while for Reps the card is only authorized and payment is processed later by your accounting system. 
• Customer's card details may be saved, so they don't have to re-enter them next time
• Duplicate payments should be prevented and notification pop up presented to the user.

 

Go to Settings -> iPaaS -> Quick Setup

Install - click Install if it is not yet installed

Launch - click Launch if it is already installed

 

 

General Tab

Resource type - Define the resource Authorize logic will be applied to

Sub type - Sub Type of Resource. Please note, mandatory fields will be created for this sub type!

Mode -  Define if Production or Test Mode should be used to make the connection to your merchant account.

Merchant Details - enter your authorize.net Merchant Details. Use the guide to get help with how to get your Authorize.net credentials (MerchantName, Transaction Key, Signature Key).

 

 

Test Connection - test the connection to authorize.net

If successfully connected click Get Html icon to copy Html for Pepperi Custom Form.

 

Advanced

Generic

Merchant Name and Transaction Key

Duplicates Check

Fields Mapper

Events Listener

Visuals

 

 

Generic

 

Main

Configuration Logic

Used to define Configuration Selection Logic.
Default - use only one connected merchant and configuration.
Transaction / Activity - use transaction or activity field to get config ID.
Account - use account field to get config ID.
Query - use query param to get config ID.

This Quick Setup runs as a single UI task. In order to allow different options for different transactions / activities, it allows you to configure multiple sub configurations. This option allows to define 'selection' logic (this option is same for all sub configurations - located in particular place, so UI task can access it without knowing yet what sub config to use).

Default - UI task logic gets first sub-configuration in the list all the time (should be used if Authorize.net is used in only one Transaction/Activity).

Transaction / Activity - define a 'Configuration Selection Field Name' (same for all subconfigs) in 'Field Mapper' section below. It is the API name of field, value of which will be used as current config id.

For example:

You have a Transaction and want to use two different sub-configurations in the same Workflow, depending on business logic. Create a TSA field in that transaction and return '1' or '2'. If you return '1', then first one will be used, if '2' - second one.

Account - similar to previous, but account TSA field is used. (Different sub configs can be used for different accounts). Note, you can always replace this with a Trasnaction/Activity TSA, since you can create TSA calculated field that returns the Account field.

Query - it adds a query parameter to custom form Html code. The UI task checks this parameter. Note, if you use this and want to change any subconfig in any custom form, you should replace custom form code (can be replaced only ID in query - you an get it from top-right menu). Changing from any other to Query requires custom forms replacement.

 

Payment Type

Used to define Payment Type.
Authorize- this parameter instructs Authorize.net to authorize the amount but not capture it on the customer's card.
Authorize and Capture- used to first authorize and capture amount on the customer's card.

Currency - the currencies defined in your authorize.net account will be displayed. For multiple currencies, create a sub-configuration for each currency.

Enable Save Cards - 

Yes - allows to use "Pay With Selected Card" option (Creates Account TSA Field for saving Authorize Customer ID, then use it to store cards in Authorize)

No - card must be re-entered each time

Always create Customer - 

Quick Setup creates Authorize.net Customer only when the user chose to pay with card saving. Enabling this option allows to create Customer in case payment was proceeded.

 

Notifications

 

 

Approved Notification

Message - text shown in pop up after successful payment

Time to Close (ms) - time in ms until auto-close

Duplicates Notification

Message - test shown in pop up when duplicate is detected

Time to Close (ms) - time in ms until auto-close

Should Auto Close

Yes -

No - 

Use Save and Close Logic 

Yes - 

No - 

Show Success Notification

Yes - 

No -

 

 

Merchant Name and Transaction Key

Saved from the General Tab (see above)

 

Duplicates Check

 

 

Should Check Duplicates

Yes - check Pepperi's UDC for duplicate payments

No - duplicate payments will not be checked

Should Use Webhooks

Yes - use authorize.net webhook to check duplicates (if webhook does not exist in authorize.net account, Pepperi will create it)

No - duplicate payments will be checked within Pepperi, using UDC.

Webhook Signature Key - if webhook is enabled, copy the key from the webhook information in your authorize.net account

 

Fields Mapper

Map fields for data storage.

 

Field Mapper General - 

Transaction Approve ID - Pepperi Transaction TSA Field Name, that corresponds to setting
Authorize.net payment ID back to Pepperi Transaction after payment.
In case of empty, Transaction will not be updated.
Type: String / Single Line Text
Default Value: TSAAuthorizeTransactionApproveID

Authorize.net Customer ID - Pepperi Account TSA Field Name, that corresponds to saving
Authorize.net Customer in order to enable saving cards.
Used only if Enable save cards set to true
Type: String / Single Line Text
Default Value: TSAAuthorizeCustomerID

Grand Total - Pepperi Transaction / Activity Field Name, used to get payment Total
Type: Number
Default Value: GrandTotal

 

Configuration selection Field name - Used to define field name or query param name that will be used in case of Transaction, Account or Query Selection Logic.

In case of:
1) Transaction - will make api request to get transaction field with sub configuration ID
2) Account - request to get Account field
3) Query - will get it from query param with that name
4) Default - not in use, will take first configuration
Fields type should be Number Integer (not String, 2 !== '2')
Default Value: subConfigurationId

 

Transaction Task Log ID - Pepperi Transaction TSA Field Name to store task log id for Authorize.net Webhook. Used only if Webhooks are enabled

Type:Single Line Text
Default Value: TSATransactionTaskLogID

 

Transaction Unique ID - Pepperi Transaction TSA Field Name to store unique ID for Authorize.net Webhook. Used only if Webhooks are enabled

Type:Single Line Text
Default Value: TSATransactionUniqueID

 

Field Mapper Cards - 

 

Update Pepperi Card ID - Pepperi Transaction / Activity Field Name, used to update Transaction with card ID. If you do not enter a field name, this value will not be updated in the Transaction/Activity.
Default Value: TSAAuthorizeCardID

Update Pepperi Card Brand - Pepperi Transaction / Activity Field Name, used to update Transaction / Activity with card Brand.
Possible values: amex, diners, discover, jcb, mastercard, visa, or unknown.
If you do not enter a field name, this value will not be updated in the Transaction/Activity.
Default Value: TSAAuthorizeCardBrand

Update Pepperi Card Last 4 Digits - Pepperi Transaction / Activity Field Name, used to update Transaction / Activity with card last 4 digits in '1234' format.
If you do not enter a field name, this value will not be updated in the Transaction/Activity.
Default Value: TSAAuthorizeCardLast4Digits

 

Events Listener

Enter code to run at the Init Start and Init End

Enter code to run before API calls and Get Data calls in the UI Task

Visuals

The Visuals section allows you to select the colors and borders for the payment window graphics. You can preview the window for Desktop/Tablet/Mobile devices.

 

Select the colors according to your branding: