Introduction for API

This guide describes the Web development required to connect an application to the MerchantPlus Payment Gateway in order to submit credit card transactions for authorization using the Application Programming Interface (API).

API is a customizable payment processing solution that gives the merchant control over all the steps in transaction processing. To list a few, the following are the controls depending on the merchant’s business requirements:

Collecting customer payment information through a custom application.
Generating a receipt to the customer.
Secure transmission of data to the payment gateway for transaction processing.
Securely storing cardholder information, ..etc.

Minimum Requirements

Before you begin, check with the merchant to make sure that the following API requirements have been met. It is strongly recommended that you work closely with the merchant to ensure that any other business and Web site requirements (for example, bank or processor requirements, Web site design preferences) are included in their API integration.
The merchant must have a U.S.-based merchant bank account that allows Internet transactions.
The merchant must have a MerchantPlus (Card Not Present) Payment Gateway account.
The merchant must be able to store payment gateway account data securely (for example, Login ID, or Transaction Key).

Features of API

In addition to basic transaction processing, API provides merchants with several features for configuring transaction security options and further customizing their customers’ checkout experience. These features are listed in the API feature selection table below. Take a few moments to discuss these features with your merchant and select the appropriate features for their integration.

Feature	Description	Requirements
Address Verification Service (AVS) Filter	This feature enables merchants to compare the billing address submitted by the customer for the transaction with the address on file at the card issuing bank. Filter settings in the Merchant Interface allow the merchant to reject transactions based on the AVS response received.	To implement AVS, the merchant must require the Address and ZIP Code fields on their custom payment form. For more information about AVS, see the Merchant Integration Guide at http://www.Merchantplus.com/ support/merchant/
Card Code Verification (CCV) Filter	This feature enables merchants to compare the card code submitted by the customer for the transaction with the card code on file at the card issuing bank. Filter settings in the Merchant Interface allow the merchant to reject transactions based on the CCV response received.	To implement CCV, the merchant must require the Card Code on their custom payment form. For more information about CCV, see the Merchant Integration Guide at http://www.merchantpluse.comt/ support/merchant/
Itemized Order Information	This feature enables merchants to submit details for items purchased. This information is included in the customer’s confirmation email, in the Transaction Details for the transaction.	To implement Itemized Order Information, the line item field must be submitted for each transaction.
Email Receipt	This feature enables merchants to have the payment gateway send an automatic email receipt to their customers.	To configure the payment gateway email receipt, merchants must require the customer email addresses on their custom payment form, and settings must be configured in the Email Receipts section of the Settings menu in the Merchant Interface or submitted for each transaction.

Developer Support

Several resources are available to help you successfully integrate a merchant Web site or other application to the MerchantPlus Payment Gateway.

Email our Integration Team for test accounts or developer questions via email at support@merchantplus.com.