Merchant Accounts records define the components necessary to successfully complete an electronic payment transaction. The record information includes:

• The components necessary for Aptify to contact the gateway provider.
• The interface parameters required to communicate with the gateway provider once a connection has been established.
• Other parameters for interpreting the data sent to and from the gateway provider.
• The payment types that will be submitted to this merchant for verification.
  
  

The standard Aptify installation includes two Merchant Accounts records:

• A sample record that illustrates how the ePayment feature works using a sample component (this provides a sample for developers who need to create new merchant account interfaces for their organization).
• A PayPal merchant account that can be used by an organization that has a PayPal PayFlowPro account. See Creating and Configuring Merchant Accounts for more information on the PayPal account.

Additional Parameters Tab

Lists the additional parameters for this merchant account. This feature enables an organization to pass additional data (besides fraud mappings) to include in a merchant account transaction. These parameters are only applicable when the Use Additional Parameters option is selected. See About the Merchant Account Additional Parameters Form for more information.

Attachments Tab

The Attachments tab lists any files relevant to the Merchant Accounts record.

Attributes Tab

Lists the merchant attributes for the merchant account. These attributes determine how Aptify communicates with the third-party merchant. See About the Merchant Account Attributes Form for information on an Attributes sub-type record.

Fraud Mappings Tab

Lists the merchant account fraud mappings for this merchant account. This feature enables an organization to perform real-time authorization and fraud evaluation while helping to distinguish between legitimate shoppers and fraudulent users in a single transaction request. These mapping are only applicable when the Fraud Check Level is set to Low, Medium, or High. See About the Merchant Account Fraud Mappings Form for information on an the mappings sub-type record.

Currency Types Tab

This tab stores the set of currency types supported by this merchant account. See About the Currency Types Form for Merchant Accounts for information on the sub-type form that can be accessed from this tab.

General Tab

Displays the basic information needed to interface with all gateway providers.

Merchant Account Name (Required)

The name for the merchant account record. This is for reporting and recognition purposes only and should be descriptive enough to help the user understand which merchant account is in use.

Organization

The organization that links to this merchant account record. Usually this will be the main organization's record. In cases where clients are utilizing Aptify's multi-entity accounting, this field specifies which entity is linked to the merchant account. This field links to the Organizations service.

Manager

The manager of this merchant account. This is used for reporting purposes and specifies the person responsible for managing the details of the merchant account, such as an accounting employee responsible for credit card agreements. This field links to the Employees service.

Authorization Type (Required)

The manner in which the Authorization Object processes authorization attempts. The options are AuthOnly, AuthCapture and OrderSpecific. The AuthOnly authorization type supports the sale of products that do not immediately ship to a customer (AuthOnly transactions are captured later using the ePayment Capture wizard). The AuthCapture authorization type supports the sale of products that ship immediately or virtually ship (such as memberships, subscriptions and meeting registrations). OrderSpecific is not supported in the current release.

Fraud Check Level (Required)

The level of reporting requested if fraud-checking is implemented. The options are Off, High, Medium, and Low. This field must be set to a value other than Off to enable fraud checking. In Aptify, a value of Low, Medium, or High all enable fraud checking. The fraud checking tolerance level is set by the Fraud Check Threshold.

The fraud checking feature enables an organization to perform real-time authorization and fraud evaluation while helping to distinguish between legitimate shoppers and fraudulent users in a single transaction request. Note that an organization typically must subscribe to the merchant account's Fraud Prevention services to successfully utilize this feature.

Fraud Check Threshold

This field specifies the threshold for when a payment should be failed based on fraud evaluation criteria. It is only applicable when the Fraud Check Level is set to Low, Medium, or High.

When a merchant processes a payment request, it calculates a fraud check score for the payment (based on the fraud mappings which specify the set of data that Aptify passes to the merchant for evaluation). The lower the score, the greater the likelihood that the payment attempt is fraudulent. This score is then returned to Aptify. Aptify compares the payment's score against the threshold. If the returned score is equal to or less than the threshold, then the payment fails.

In Aptify, fraud scores are on a scale of 1 to 10. The threshold for failing a payment based on the fraud check is on a scale of 1 to 9 (since payments with a perfect fraud score should never fail). Note that merchant accounts may have different fraud score ranges, so all scores returned to Aptify will be normalized to Aptify's 1 to 10 range. For example, PayPal returns a fraud range between 1 and 199. Therefore, when PayPal returns a score to Aptify, the system divides the value by 10 so it conforms to Aptify's scale.

Do AVS Check?

Specifies whether Address Verification Service (AVS) messages should be utilized or ignored.

AVS Threshold

This field specifies the threshold for when a payment should be failed based on the results of an address verification match. When a merchant processes a payment request, it may attempt to verify the address provided by the customer against the address on file for the provided account (such as a credit card account). The merchant system then returns this information to Aptify.

Aptify converts the AVS check information in a numeric score, from 0 to 10. If the AVS score is equal to or less than the AVS threshold, then the payment fails.

The AVS Threshold supports a scale from 1 to 9. The higher the threshold, then the less tolerant the merchant account on AVS results.

PayPal's AVS results are based on an Address and ZIP Code match. When Aptify received AVS information from PayPal, it assigns a score from 1 to 10 based on the following criteria:

• If the AVS service is unavailable, the assigned score is 3.
• If both the Address and ZIP Code match, the assigned score is 10.
• If the ZIP Code matches but the Address does not, the assigned score is 7.
• If the Address matches but the ZIP Code does not, the assigned score is 5.
• If neither the address or ZIP Code match, the assigned score is 0.

Is Active?

Specifies whether the merchant account is active or inactive. If not selected, all configured payment types are ignored for this merchant account.

Use Aptify Reference Number?

Specifies whether or not subsequent transactions (after the initial authorization) should utilize the Aptify Reference Number or the Processor-provided Reference Number.

Do CSC Check?

When this option is selected, Aptify send the credit card security number provided by the customer to the merchant for verification. This security number is the three- or four-digit number that appears on credit cards in addition to the account number. It is also known as the Card Verification Value code (CVV) or as the Card Security Code (CSC). Depending on your organization's business rules, a customer or order entry clerk may need to enter the security number as part of the credit card authorization process.

Use Additional Parameters

When this option is selected, Aptify sends can pass additional parameters (in addition to or other than Fraud Checking) to your organization's merchant account, which are stored on the Additional Parameters tab. See About the Merchant Account Additional Parameters Form for more information.

Use Reference Transactions

When this option is selected, Aptify processes reference transaction-based credit card payments. See About the Credit Card Reference Transaction Payment Type for more information on using this type of payment.

Payment Types Tab

Lists the merchant account payment types for this merchant account. When a payment type is selected in an order, all active merchant accounts are evaluated and the one with the payment type listed on this tab is used when contacting the gateway provider. This tab links to the Merchant Account Payment Types record. See About the Payment Types Form for Merchant Accounts.

PlugIns Tab

Authorization Assembly

The .NET assembly name of the object that allows Aptify to communicate with this merchant account's system for the purpose of authorizing payments.

Authorization Object

The location in the Aptify Object Repository of the object that allows Aptify to communicate with this merchant account's system for the purpose of authorizing payments.

Authorization Class

The class within the Authorization Object that provides the functionality to authorize payments with this merchant account. This class should be based on Aptify's ElectronicPaymentBase class. See the Aptify Software Development Kit (SDK) for details.

Capture Assembly

The .NET assembly name of the object that allows Aptify to communicate with this merchant account's system for the purpose of capturing payments.

Capture Object

The location in the Aptify Object Repository of the object that allows Aptify to communicate with this merchant account's system for the purpose of capturing payments.

Capture Class

The class within the Capture Object that provides the functionality to capture payments with this merchant account. This class should be based on Aptify's ElectronicPaymentBase class. See the Aptify Software Development Kit (SDK) for details.