Support Documentation

Swipebox Gateway 1.0

  1. Swipebox Gateway Overview
    1. Merchant Payment Processing Environments
    2. Payment Gateway Core Features
    3. Payment Types & Acceptance Methods
    4. Back Office Tools
  2. ACH-Overview
    1. Why Should I Use ACH?
  3. Getting Started with Apple Pay In-App Purchase
    1. How Does Apple Pay In-App Purchase Work?
    2. How Do I Configure Apple Pay?
    3. How Do I Integrate Apple Pay into My Mobile App?
  4. ATRI (Load Balancing) Guide
    1. What is ATRI?
  5. Batch ProcessingGuide
    1. How does Batch Processing work?
    2. How do you upload batch files?
    3. How do you Configure Formats?
  6. Certify-PCI-Overview
    1. Overview
  7. Customer Vault Guide
    1. Customer Vault Overview
    2. Customer Vault Process Flow
    3. Value Proposition
  8. Electronic-Invoicing-Overview
  9. iProcess-Overview
    1. iPS-Enterprise-Overview
      1. Features
    2. Mobile-Only-Overview
  10. iSpyFraud-Overview
    1. iSpyFraud Detailed Guide
      1. What is iSpyFraud?
      2. Getting Started
      3. Thresholds Tab
      4. General Tab
      5. User Ban Tab
      6. Exceptions Tab
      7. Waiting Review Tab
      8. History Log Tab
      9. Frequently Asked Questions
    2. iSpyFraud - Merchant Cases
      1. Case One: Restrict Transactions from Outside of Your Country
      2. Case Two: Protect Yourself from Card-Spinning/Card-Testing Fraud on your ecommerce website
      3. Case Three:Protect Yourself from Employee Fraud
      4. Case Four: You Have Multiple MIDs but Don’t Want Your Transactions Scrubbed on Every MID
      5. Case Five: You Process Recurring Transactions and Don’t Want to Accept Pre-Paid Cards
      6. Case Five: You Process Recurring Transactions and Don’t Want to Accept Pre-Paid Cards
  11. Multi-MIDs-Overview
  12. Payer Authentication (VbV/MCSC) Guide
  13. Product Manager Guide
    1. What is Product Manager?
    2. How does Product Manager Work?
  14. Recurring-billing-overview
    1. Recurring Billing Guide
      1. Overview
      2. How to edit established recurring billing for a single cardholder or a checking account
      3. How to edit established recurring billing
      4. How to create billing plans for an unlimited number of cardholders or checking
      5. How to edit billing
      6. How to create recurring billing with batch upload
  15. SwIPe-Overview
  16. SyncPay-Overview
    1. QuickBooks SyncPay Guide
      1. How do I export transactions to Quickbooks™?
  17. Gateway-Comparison-Chart
  18. VAS-Suite-Overview
    1. Data Security & Fraud Detection
    2. Payment Types & Acceptance Methods
    3. Back Office Tools
  19. Two-Factor-Auth-Overview
  20. Virtual Terminal
    1. Virtual Terminal Guide
      1. Customization
      2. Recurring Billing
      3. Batch Upload
      4. Gateway Options
      5. Reports
      6. Certify PCI™
    2. Virtual Terminal Credit Card Guide
      1. How to process a sale
      2. How to authorize or capture a transaction
      3. How to void a transaction
      4. How to process a refund
      5. How to process a refund
      6. Advanced features
    3. Virtual Terminal Electronic Check Guide
      1. How to process a sale
      2. How to process a sale
      3. How to void a transaction
      4. How to process a refund
      5. Advanced features

Swipebox Gateway Overview

 

Yes No

Merchant Payment Processing Environments

Yes No

Payment Gateway Core Features

Yes No

Payment Types & Acceptance Methods

Yes No

Back Office Tools

Yes No

ACH-Overview

Why Should I Use ACH?

Yes No

Getting Started with Apple Pay In-App Purchase

 

Yes No

How Does Apple Pay In-App Purchase Work?

Apple Pay provides an easy and secure way for your customers to buy goods and services such as groceries, clothing, tickets, and reservations within your iOS 8 app by using payment information stored in Passbook on your customer’s iOS device.

Using Apple’s Touch ID technology, your customers can authorize payments using the credit and debit card payment credentials stored on their iPhone 6 or iPhone 6 Plus. These models contain a Secure Element, isolating card payment credentials from where your mobile app runs.

When a customer makes an Apple Pay “In-App” purchase, the following steps take place before the payment can be completed:

  1. The merchant’s app interacts with the Apple PassKit Framework to obtain encrypted payment data.
  2. The merchant’s app forwards the order information along with the encrypted payment data to the merchant’s web server.
  3. The merchant’s web server sends the encrypted Apple Pay payment data to the gateway using the Mobile SDK, or the Direct Post API.
  4. The payment gateway decrypts the payment data and processes the transaction.

In summary, merchants must obtain the Apple Pay encrypted payment data within their app using PassKit. Once received, the Apple Pay encrypted payment data is then sent to the payment gateway API for processing instead of actual credit card information.

Yes No

How Do I Configure Apple Pay?

Creating an Apple Merchant ID

First, you must obtain an Apple Merchant ID before you can generate the Certificate Signing Request (CSR) that Apple requires. You will need to set up an Apple Merchant ID in your iOS Developer account, follow these steps to complete the setup:

  1. Go to Apple’s Developer Portal and log in to the Member Center to create a new Merchant ID.
  2. Navigate to the Certificates, Identifiers, and Profiles area of the Member Center, and then begin the Register Merchant ID process.
  3. You must then “set” the Apple Merchant ID within your gateway Control Panel under Settings, Apple Pay.

Generating the CSR

Next, you will need to associate a Certificate with the Apple Pay Merchant ID in Apple’s Developer Portal. After Downloading the Certificate Signing Request from the gateway’s options page, follow these steps:

  1. In Apple’s Developer Portal, click on the Merchant ID and then click “Edit”.
  2. Click “Create Certificate”.
  3. You are obtaining a CSR file from a Payment Provider so you will not have to create one. Click “Continue” to proceed to the upload page.
  4. Click “Choose File…” and select the Gateway.cert Signing Request file you downloaded from the gateway’s options page.
Yes No

How Do I Integrate Apple Pay into My Mobile App?

Once the Apple Merchant ID and CSR have been configured, you must integrate your app into Apple’s PassKit framework in order to obtain the Apple Pay encrypted data as described above.

To learn more about the technical details of sending Apple Pay encrypted data to the payment gateway API, please visit the Apple Pay section of the Integration Portal where a sample application is available for download as well.

Yes No

ATRI (Load Balancing) Guide

What is ATRI?

ATRI stands for Advanced Transaction Routing Interface and provides the merchant with load balancing functionality across an unlimited number of MIDs.

Credit Cards

Transactions can be automatically routed to maintain the dollar amount or percentage allocated.

Merchant Defined Field Transaction Routing

Merchant defined fields can be used to route transactions to associated MIDs (identification). The API can be used to programmatically route transactions.

Processor

Custom descriptors can be used when adding MIDs within the Virtual Terminal. Users can manually select an individual MID to route a transaction.

Yes No

Batch ProcessingGuide

How does Batch Processing work?

With the Batch Upload function, .XLS, .TXT, .CSV files can be uploaded for processing. These files can contain a mixture of transaction types within the files themselves including sales, credits that would be the commission payments, credit card and ACH charges.

The file template can be saved for subsequent processing.

The individual transaction details are displayed in the below examples to provide the invoice/commission recipient with reconcilable line details.

Invoice

Commission Payment File Sample

Yes No

How do you upload batch files?

When uploading batch files, 50,000 transactions can be run within 90 minutes.

Step 1:Click on Batch Upload from the Main Menu

Step 2:Click Choose File to select the file that you wish to upload

Merchants can create a .CSV, .XLS, .TXT transaction file to upload for processing. When creating this file, transactions can be mixed (i.e. auth, credit, sale, etc.)

Step 3:Select Format from one of the two options available

Option 1:Auto Detect File Format will intelligently read the information within the file allowing the user to confirm the type of information in the respective field.

Option 2: Use Selected Format.

Step 4:Using Auto Detect

Auto Detect determines the field names based on the uploaded file. Fields with red asterisks are required fields as set by the Affiliate.

Yes No

How do you Configure Formats?

There is also an option to create a format for your batch files. Configuring batch formats will allow the system to identify order and field types you commit.

Step 1:Select the Configure Formats icon from the top menu in the Batch Uploads feature

Step 2:Click Add Batch Format

Step 3:Configure the settings for a new file format

Note: Fields with red asterisk are required fields set by the Affiliate

Step 4:Click Save to complete after filling out all the necessary fields

Step 5:File format has been successfully added

Step 6:New file format is listed under the Batch Upload File Formats menu. Options to View, Edit, Delete or Make Default are available. Click View to see the configuration.

Step 7:From the view menu, the merchant also has the option to edit the file format. Click Edit to access the file format’s configuration menu.

Yes No

Certify-PCI-Overview

Yes No

Overview

  • CertifyPCI™ is an in-house automated web-based PCI tool that provides an easy way to PCI certify qualified merchants and agents.
  • Using payment applications that support PCI Data Security Standards (DSS) compliance mitigates emerging security risks.
  • CertifyPCI™ is the first and only gateway integrated PCI Compliance software that will provide a client with a turnkey e-commerce solution inclusive of PCI certification.
  • Committed to streamline that process for merchants and agents to achieve and maintain a high security posture for their businesses.
  • Offers a $50,000 per occurrence insurance for merchants and agents should there be a compromise incident.
  • With PCI compliancy status, we allow merchants to unlock sensitive payment information after they have provided the gateway, a current and valid PCI acceptance certificate and are approved by a gateway administrator.
Yes No

Customer Vault Guide

Customer Vault Overview

Security Concerns

The Customer Vault was designed specifically for businesses of any size to address concerns about handling customer payment information. Visa and MasterCard have instituted the Payment Card Industry (PCI) Data Security Standard to protect cardholder data–wherever it resides–ensuring that members, merchants, and service providers maintain the highest information security standard.

These associations have also deemed that merchants will be held liable for any breach of cardholder data. This has become a major concern for merchants who may handle credit card or electronic check payments, but are looking to avoid the tremendous costs and resources involved in becoming PCI compliant.

Customer Vault Solution

The Customer Vault allows merchants to transmit their payment information through a Secure Sockets Layer (SSL) connection for storage in our Level 1 PCI certified data facility. Once the customer record has been securely transmitted to the Customer Vault, the merchant can then initiate transactions remotely without having to access cardholder information directly. This process is accomplished without the merchant storing the customer’s payment information in their local database or payment application.

Furthermore, using the gateway’s3 Step Redirect Method in conjunction with the Customer Vault allows merchants to process transactions without transmitting any payment information through their web application. This unique approach provides best of class application flexibility without any PCI compliancy concerns. The 3 Step Redirect API (Advanced Programmers Interface) is available by request of the project manager.

Yes No

Customer Vault Process Flow

An initial Customer Record creation using the Customer Vault

  1. The Cardholder securely submits sensitive payment details directly to the Customer Vault.
  2. The Payment Gateway performs the requested operation and the results of the transactions are returned to the Merchant’s web application. Simultaneously, a Customer Vault token of “12345” which contains all customer data including payment details is created.
  3. The Merchant’s web application displays the appropriate message to the customer as to whether the transaction was approved or declined.

30 days later, Merchant wishes to charge the customer again using Customer Vault token “12345”

  1. The Merchant’s web application connects to the Customer Vault and remotely loads customer record “12345” to initiate a $50.00 charge.
  2. The Payment Gateway processes the transaction and responds to the merchant with the transaction response from the processor(s).
Yes No

Value Proposition

Value Proposition

who utilize the Customer Vault can process transactions and maintain an up-to-date customer Merchants database without storing any customer payment details. All sensitive customer data was transmitted through encrypted channels and authorizations, captures, refunds and settlements were managed remotely without storing any cardholder data locally. This gives the merchant unparalleled application flexibility while shifting its liability of PCI compliancy.

The Customer Vault can store both credit card and electronic check payment details. Access to the Customer Vault is granted through a secure online interface. The interface specification is described by an API (Advanced Programmers Interface) Integration Manual which is sent by request to the project manager. The Customer Vault and Payment Gateway interface has been Level 1 PCI compliant since 2004.

Yes No

Electronic-Invoicing-Overview

Yes No

iProcess-Overview

Yes No

iPS-Enterprise-Overview

Yes No

Features

Features

  • Supported Devices: Apple and Android based devices.
  • Secure card reader connects to all mobile devices via the headphone jack.
  • Combines the latest technologies for reliable and secure mobile payments and identification.
  • Swipe path design yields highest read reliability on first pass.
  • Track 1 and 2 data.
  • Card reader uses dynamic encryption, tokenization and authentication, which meets PCI P2PE (Point to Point Encryption) guidelines for mobile payments.

iProcess™ Mobile Application Update Required

Merchants must update their iProcess™ mobile application to be compatible with the iPS Enterprise Encrypted Mobile Card Reader. The update will be provided through the App Store and Google Play and is compatible with all supported card readers.

Yes No

Mobile-Only-Overview

Yes No

iSpyFraud-Overview

Yes No

iSpyFraud Detailed Guide

What is iSpyFraud?

What is iSpyFraud?

Welcome to the detailed user guide for iSpyFraud, a rule-set based fraud management utility that allows merchants to configure extensive filters to aid in the detection of fraud by screening transactions throughout the processing lifecycle. As it operates in real time, iSpyFraud can decline transactions both before and after authorization, which can potentially mitigate high chargeback volume and offer merchants peace of mind when it comes to their own security, as well as that of their customers.

Basic Uses

Though there are countless ways to use iSpyFraud based on varying scenarios merchants might encounter, there are certain uses of the software that could be considered universally relevant, including:

  1. Monitoring and controlling transactions during a given timeframe by setting rules based on a combination of many parameters, including the following:
    1. Transaction count
    2. Transaction a
    3. IP address
    4. User location
    5. Credit card number
    6. Credit card brand
  2. Limiting internal credit card fraud or abuse attempts
  3. Blocking transactions from specific countries
  4. Reviewing suspect transactions in order to take action prior to settlement

The following instructions will aid merchants in choosing the settings that will prove most useful for them depending on the specific needs of their business. In addition to this guide, assistance can be accessed through our support team, which can be reached at (800) 617-4850 ext. 1from 8 am-6pm central time, or at support@nmi.com.

Yes No

Getting Started

  1. mountWhen a merchant logs into the gateway, iSpyFraud can be found as a link under “Other Services” on the left side of the page. The link will take the merchantto the program’s General tab.

Other than geography bans on transactions from certain countries, there are no default settings in place. There are default geography bans on the following countries (as sent in the Country field):

Afghanistan

Albania

Armenia

Azerbaijan

Bulgaria

Czech Republic

India

Indonesia

Iran (Islamic Republic of)

Kazakhstan

Kuwait

Lithuania

Macedonia, the Former Yugoslav Republic of

Malaysia

Pakistan

Romania

Russian Federation

Turkey

Ukraine

Viet Nam

Yugoslavia

The countries on this list are frequently the origin of fraudulent international transactions. The merchant can remove any of them from the ban list at will (see User Ban tab section for instructions).

Yes No

Thresholds Tab

The Thresholds tab allows a merchant to set a variety of parameters on attempted or approved transactions, and these rules give the merchant the option to either Flag for Review or Deny Transaction. There are two main sections, titled Add/Edit Credit Card Rules and Add/Edit IP Address Rules, and the options in each section direct the merchant to set a threshold on a certain aspect of a transaction. These thresholds can be set in a combination of ways to track and/or block certain types of activity that may point to fraud.

For example, there are two rules pertaining to single transaction amount. If the merchant doesn’t sell anything under $20, they can set transactions for anything less than $20 to be flagged for review or denied. This can help prevent card testing, in which a fraudster might charge small amounts to a large number of credit cards.

In another case, a merchant with a subscription-based business might use the option to limit attempted number of transactions; the merchant can flag for review transactions beyond the initial subscription fee that come from the same IP address within the same day to ensure that they’re not fraudulent.

To set thresholds, the merchant simply chooses (if applicable) whether they wish to screen attempted or approved transactions (drop-down), enters the desired values, and then chooses whether the end result of a suspicious transaction should be to flag it for review or deny its approval (dropdown). Once these choices have been made, the merchant clicks “Update.” Each rule must be updated individually.

For a more in-depth look at somepossible uses of the Thresholds tab, see Use Cases.

Yes No

General Tab

The General tab gives basic information about what iSpyFraud does and has a brief overview of its contents. Note the tabs at the top of the screen, which browse to different sections within the iSpyFraud console.

Yes No

User Ban Tab

The bans/flags in this tab are considered static, in the sense that they don’t depend on the behavior of the user (the consumer). In each section, the merchant chooses what users or types of users to ban/flag, and any transactions originating with those users will either be banned outright or flagged for review, depending on the merchant’s selections. Each section gives the option to View current bans and Add new bans. When the merchant clicks to the “View” screen, they also have the option to Delete any currently banned users.

There are seven sections in the User Ban tab:

  1. IP Addresses
    1. Merchants can ban/flag a single IP, multiple IPs from the same block, or a range of IPs
    2. Merchants can specify a timeframe (number of days) in which to ban/flag IPs, or make the ban/flag indefinite
  2. Credit Cards
    1. Merchants can ban/flag a single credit card number, multiple credit card numbers, or all credit card numbers with matching BINs
    2. Merchant can specify a timeframe (number of days) in which to ban/flag credit card numbers, or make the ban/flag indefinite
  3. Geographical Information
    1. Merchants can ban/flag transactions from any country
    2. Merchants can specify a timeframe (number of days) in which to ban/flag a country, or make the ban/flag indefinite
    3. A ban/flag on a specific country will automatically check forany billing/shipping addresses from that country and ban/flag users based on that information, and the merchant can also choose whether or not to verify IP addresses from that country
  4. US/Non-US IP Ban
    1. Merchants can choose three actions (Nothing, Ban, or Flag for Review) for transactions that have a billing country of US but a source IP address outside the US
      1. Unlike with the other sections in this tab, there is no timeframe specified for this ban
      2. Merchants who do not send the Country field with their transactions can set a US Country Default, which will assume (for the purposes of this particular ban) that the Billing Country is the US.
    2. User Information
      1. Merchants can ban/flag specific customers based on customeruser IDs, which merchants can assign via the use of Customer Vault. User IDs outside of Customer Vault can also be submitted by the merchant via API or by providingthe billing email in the transaction
      2. Merchants can specify a timeframe (number of days) in which to ban/flag certain users, or make the ban/flag indefinite
    3. Email Address
      1. Merchants can ban/flag customers by email address, or ban/flag any customer using an email address with a particular domain
      2. Merchants can specify a timeframe (number of days) in which to ban/flag certain emails or domains, or make the ban/flag indefinite
    4. Batch Ban
      1. Merchants can upload up to 5000 entries for a specific ban type at once
      2. Types can be chosen using the radio buttons above the Batch Data Box—merchants can select from IP/Range, Credit Card/Bank, User ID, and Email
        1. Only one type of data may be uploaded at a time
      3. Merchants can specify a timeframe (number of days) in which to ban/flag certain values, or make the ban/flag indefinite

Note: For any of the IP Address selections to work, the Merchant must collect the public-facing IP address from the consumer and provide it with the transaction.

For a more in-depth look at somepossible uses of the User Ban tab, see Use Cases.

Yes No

Exceptions Tab

The Exceptions tab goes hand in hand with the User Ban tab, and is considered the “whitelist” to the User Ban’s “blacklist.” In other words, merchants can use the Exceptions tab to make concessions for certain known users that would otherwise be banned or flagged under the restrictions in the User Ban tab.

Any exception overrules all other rules. For example, if credit card 4111111111111111 is added to exceptions, the domain @gmail.com is banned, and the country Canada is banned, a transaction using “4111111111111111, test@gmail.com, and Canada” will be approved.

Merchants can create exceptions for

  • IP Address
  • Credit Card
  • User ID
  • Email Address

Exception values can also be uploaded using the same process as batch bans.

Yes No

Waiting Review Tab

Merchants can view and take action on flagged transactions here; merchants can either voidtransactions that are in waiting review or allow them to settle by indicating that the review is complete. If no action is taken, transactions awaiting review will settle at the time set in the Merchant’s Settlement Schedule.

Merchants will be able to see which rule triggered the review.

Yes No

History Log Tab

The History Log offers the merchant a searchable record of all transactions scrubbed by iSpyFraud. This log is useful for a merchant who is trying to assess the risk of potential fraud, or to evaluate known fraud patterns. A drop-down menu allows merchants to limit a search by time/date of transaction, and merchants can search by transaction ID, credit card number, email address, or IP address.

The log is color coded by transaction status: Accepted (green), Review (yellow), Exception (blue), or Denied (red). For statuses of Review and Denied, a magnifying glass next to the response status allows merchants to see which rule was triggered.

Yes No

Frequently Asked Questions

Q: What types of merchants need iSpyFraud?

A: Though all merchants can benefit from the reassurance a fraud scrubbing utility offers, it’s true that some merchants are more likely to be targeted by fraudsters than others. Forexample, merchants who process international transactions are considered higher risk, as are those in certain verticals, such as online gambling, online dating, membership-only websites with adult content, or even unexpected ones like consumer electronics. Non-profits that accept donations are also at risk and can benefit from iSpyFraud, as they are often used by fraudsters for card testing/spinning schemes.

It’s also anticipated that as EMV cards become standard in card present transactions, there will be a rise in card not present fraud, meaning more e-commerce merchants will be at risk. iSpyFraud is an ideal solution to combat the predicted spike in online credit card fraud.

Q: Does iSpyFraud work in card present transactions?

A: Although iSpyFraud was originally designed for e-commerce, it works equally well for card present transactions. The software’s thresholds and rules do not discriminate between retail and keyed transactions, nor is the utility’s scrubbing ability restricted by transaction origin (API, Virtual Terminal, Batch Upload, etc.).

Q: Can iSpyFraud block someone from coming to my website?

A: No, iSpyFraud can only take action on transactions sent to the Gateway. It cannot block activity happening on a website prior to data being sent to the gateway. Merchants can speak to their hosting provider or web developer if they need to block an individual from accessing their website entirely.

Q: I’d like to use iSpyFraud on my website, but I don’t want to use the Gateway to process. Is this possible?

A: No, iSpyFraud is an additional service that can be added onto a gateway account to scrub transactions processing through it. It cannot be used as a standalone service. Merchants must be processing through the gateway to take advantage of the iSpyFraud scrubbing service.

Yes No

iSpyFraud - Merchant Cases

Case One: Restrict Transactions from Outside of Your Country

Merchants can use iSpyFraud to restrict transactions outside their own country in two ways:

  1. User Ban>>Geographical Information>>Verify Country
    1. Using the Verify Country option, merchants can select to only look at the customer’s billing/shipping addresses. This would prevent any transaction with a billing or shipping address outside the merchant’s country from being processed (merchant can choose to either ban or flag for review)
    2. To ban/flag all countries other than their own, the merchant would simply highlight all countries except their own from the list in the Geographical Information section of the User Ban tab, then click “Add”.
  2. User Ban>>Geographical Information>>Verify IP Addresses
    1. If a merchant chooses to verify IP addresses in addition to billing/shipping addresses, iSpyFraud will also weed out transactions where the IP Address is physically located in the banned/flagged country.
    2. This option can only be selected in addition to the Verify Country option. Using both together is the safest method of screening for location by country, as a fraudster’s physical location often does not match the submitted billing/shipping address.

Example 1: If a merchant sells supplements but doesn’t ship internationally due to regulatory laws, that merchant would most likely want to only verify a customer’s country by billing/shipping address, rather than IP address, since the restriction they are most concerned with deals with where the merchandise goes, not necessarily where the transaction originates from. Although this provision isn’t necessarily a case of fraud, this type of setting could help prevent chargebacks.

Example 2: If a merchant is a non-profit organization that accepts donations from locals, they would most likely select Verify Country and IP Addresses. This will ensure that they are screening for users by physical location, rather than the location of the credit card owner—this is especially important in the case of entities that accept donations, as non-profits are commonly targeted by card-testing scams.

Yes No

Case Two: Protect Yourself from Card-Spinning/Card-Testing Fraud on your ecommerce website

Card spinning, sometimes called card testing or simply carding, can be spotted in a number of different ways, including:

  1. Many authorization attempts in a very short period of time
    1. If a merchant notices an unusually high amount of authorization attempts in a short amount of time, immediate evaluation of those transactions is warranted to assess whether or not fraud is occurring. The merchant should also consider contacting our support team to assist in a thorough evaluation.
  2. The first six digits of the card (BIN) for multiple transactions are the same or similar
    1. In this case, a merchant can go to User Ban>>Credit Cards and enter the suspicious BIN, followed by a “*” (e.g. “411111*) and select whether to ban or flag that particular user.
  3. The transaction amounts are very low ($.01 to $1.00)
    1. Typically, fraudsters who spin cards will first attempt a transaction for a very low amount, just to see if they can get an approval. To help screen this type of testing, a merchant can set a threshold that bans/flags transactions under a certain amount (such as $1.00). This might not be possible for certain merchants, as they might have legitimate transactions for amounts that low.
  4. A spike in declined transactions in a merchant’s reporting
    1. If a merchant notices an unusual amount of declined transactions, the best course of action may be to contact support to get help assessing whether or not there’s fraud involved, and where it might be coming from.
  5. Nonsensical names and/or emails, or the same name/email for multiple transactions in a short amount of time
    1. When something like this happens, a merchant can block the user(s) by selecting User Ban>>Email Address and enter the email(s) corresponding with the fraudulent transactions. If the merchant notices that all of the fraudulent transactions are coming from the same domain, the merchant can screen all emails from a specific domain by entering “*@emailaddress.com”.
Yes No

Case Three:Protect Yourself from Employee Fraud

Depending on the type of employee fraud and/or credit card abuse the merchant is experiencing, various actions can be taken.

  1. If employees are entering amounts that are either higher or lower than the merchant’s business requires, a minimum and/or maximum amount threshold can be implemented.
    1. To set a minimum amount threshold, go to Thresholds>>If single transaction amount is less than $[desired amount], enter the amount you want to screen for, choose the action you wish to take (Flag for Review or Deny Transaction), and click “Update”.
    2. To set a maximum amount threshold, go to Thresholds>>If single transaction amount exceeds $[desired amount], enter the amount you want to screen for, choose the action you wish to take (Flag for Review or Deny Transaction), and click “Update”.
  2. If the card abuse is related to multiple transactions, or if a merchant’s business model dictates that a customer’s credit card should only be processed once in a given timeframe (e.g. in the case of a monthly subscription-based business), the merchant can set a credit card threshold to screen for inappropriate usage.
    1. To set a credit card threshold for daily use, go to Thresholds>>If daily attempted transaction count for CC exceeds [desired amount], enter the amount you wish to screen for, choose the action you wish to take (Flag for Review or Deny Transaction), and click “Update”
      1. The same process can be done for weekly, monthly, and yearly transaction counts.
Yes No

Case Four: You Have Multiple MIDs but Don’t Want Your Transactions Scrubbed on Every MID

iSpyFraud can be used for an entire gateway account, or be customized to only screen the transactions run under a specific MID. In addition, iSpyFraud can also be customized so that any global rules are ignored on a per-processor basis.

When it comes to setting different rules for different MIDs, this can be accomplished in one of two ways. A merchant can either set global rules and then single out specific MIDs to have them bypassed by those rules, or set entirely different rules for different MIDs.

  1. To start, merchants must have at least two active MIDs boarded on their gateway account, and must be logged in as a user with permissions to all processors.
    1. When clicking through iSpyFraud tabs Thresholds, User Ban, or Exceptions, the merchant will see a subtab labeled All Processors, then a subtab for each active MID on their account.
      1. If there are rules that the merchant wants to apply to all MIDs, those rules should be set in the All Processors tab.
      2. Any rules that the merchant wants to apply specifically to a certain MID should be set under that MID’s subtab.
  • If there are no global rules and every rule is specific to a certain MID, the merchant should not customize the All Processors tab, and instead set all rules within each MID’s subtab.
Yes No

Case Five: You Process Recurring Transactions and Don’t Want to Accept Pre-Paid Cards

Prepaid cards have their uses, but when it comes to recurring transactions, some merchants may be wary of accepting prepaid cards, as there is a chance that money will run out before the timeframe for the recurring transactions expires.

  1. To prevent the use of prepaid cards, the merchant can reach out to the Card Associations to obtain a list of BINs associated with a prepaid cards and enter them under User Ban>>Credit Cards.
    1. If there are multiple BINs, the merchant can load up to 5000 entries at once into User Ban>>Batch Ban by selecting the Credit Card/Bank radio button.
  2. The merchant can also block all cards except for specific BINs by going to User Ban>>Credit Cards and ban/flag cards beginning with the first number associated with certain card brands (e.g. entering “4*” would block all Visa cards).
    1. Once the desired card brands are blocked, the merchant can go to Exceptions>>Credit Card White List and add any card numbers/BINs that the merchant wants to accept.
    2. For multiple acceptable card numbers/BINs, the merchant can go to Exceptions>>Batch White List and select the Credit Card/Bank radio button, then upload a list of acceptable cards.
Yes No

Case Five: You Process Recurring Transactions and Don’t Want to Accept Pre-Paid Cards

Prepaid cards have their uses, but when it comes to recurring transactions, some merchants may be wary of accepting prepaid cards, as there is a chance that money will run out before the timeframe for the recurring transactions expires.

  1. To prevent the use of prepaid cards, the merchant can reach out to the Card Associations to obtain a list of BINs associated with a prepaid cards and enter them under User Ban>>Credit Cards.
    1. If there are multiple BINs, the merchant can load up to 5000 entries at once into User Ban>>Batch Ban by selecting the Credit Card/Bank radio button.
  2. The merchant can also block all cards except for specific BINs by going to User Ban>>Credit Cards and ban/flag cards beginning with the first number associated with certain card brands (e.g. entering “4*” would block all Visa cards).
    1. Once the desired card brands are blocked, the merchant can go to Exceptions>>Credit Card White List and add any card numbers/BINs that the merchant wants to accept.
    2. For multiple acceptable card numbers/BINs, the merchant can go to Exceptions>>Batch White List and select the Credit Card/Bank radio button, then upload a list of acceptable cards.
Yes No

Multi-MIDs-Overview

Yes No

Payer Authentication (VbV/MCSC) Guide

What is Payer Authentication?

Payer Authentication, also known as Verified by Visa (VbV) and MasterCard SecureCode™, are security protocols developed by Visa and MasterCard that allow consumers to shop online more securely. Visa and MasterCard also give back to eCommerce businesses that enable these programs by providing chargeback protection and lower interchange rates.

How does Verified by Visa and MasterCard SecureCode work?

VbV and SecureCode enable cardholders to create a PIN (or “secure code”) and assign it to their credit card. During checkout, the Customer is prompted to enter their PIN and the cardholder’s identity can then be confirmed by their Card Issuing bank. The Card Issuer provides additional data elements to confirm the cardholder’s identity. The data elements are amended to the authorization and settlement messages, thus providing the proper benefits of VbV/MCSC.

What are the benefits of Verfied by Visa and MastercardSecureCode?

With the programs, Visa and MasterCard aim to increase consumer confidence in online shopping and reduce fraud. To encourage 3-D Secure adoption, Visa and MasterCard offer significant merchant benefits including:

  • Fraudulent chargeback protection (per the rules of Visa and MasterCard)
  • Interchange discounts averaging 20 basis points
  • Dramatic reduction in the fraud screening costs and manual review
  • Higher AOV (Average Order Value); secure, confident Customers spend more
  • Free and automatic platform upgrades
  • Expand internationally, risk-free
  • Consumer brand loyalty and security

What is the path of a Payer Authentication transaction?


Transactions from your system are routed to both the card associations, as well as the banking authentication networks via an Internet connection through the Payment Gateway. This authentication information can be accessed in real-time through the gateway’s comprehensive reporting system, allowing you to easily identify authenticated transactions and recognize fraudulent ones. Enabling authentication does not interrupt the current authorization process.

  1. During checkout, information about the cardholder is directed to the appropriate card association to check their program enrollment status.
  2. If the cardholder is enrolled, an authentication form will be displayed by the cardholder’s bank. This form will collect the password and the bank will validate it is correct.
  3. Results of authentication are returned in less than one second. The results, new data elements, are proof that the merchant authenticated or attempted to authenticate the cardholder.
  4. The transaction is then sent for authorization through typical processes and channels. The new data elements (ECI and CAVV) are also submitted during the authorization request, thus providing the appropriate benefits associated with VbV and MCSC.

Yes No

Product Manager Guide

What is Product Manager?

What is Product Manager?

The Product Manager provides a unified product database that any merchant can use to store frequently sold items for quick recall when performing new transactions.

Where can I use Product Manager?

Product Manager is available for use within the Virtual Terminal, Electronic Invoicing system, and Enhanced Data (Level III) service.

Is there an additional cost for Product Manager?

Merchants can use this new feature at no additional cost.

Yes No

How does Product Manager Work?

Enter in Your Items

Enter in your Item(s) and any associated information (SKU, Description, Category, Commodity Code, Unit, Cost, Tax and/or Discount) into the Product Manager.

Create Packages

Creating Item Packages allows you to bundle multiple items within the Product Manager and shows the associated information for the Item Package.

Use Drop Down Menu to Select Items

Your Items and/or Item Packagesare then stored in the Product Manager and can be accessed from a drop down menu, eliminating the need to key in the same product information each time (see screenshot on next page).

Auto Calculate Totals

Using the “click to set amount” function auto-calculates the total, inclusive of any tax and/or discounts and auto-populates the information into your form (see screenshot on next page).

Hide Product Manager

A new user permission has been launched for Product Manager along with an ability to hide the new interface from within the Virtual Terminal (see screenshot on next page).

Yes No

Recurring-billing-overview

Yes No

Recurring Billing Guide

Overview

The gateway supports three separate types of recurring billing options.

  1. Traditional
    • The merchant will setup and bill a single cardholder via credit card of ACH
      e-Check, a specific dollar amount on a specific day for an indefinite or specified period of time.
  1. Expanded/Plan Recurring Billing
    • The merchant creates a plan and then can associate an unlimited number
      of cardholders with the plan.
    • The plan approach provides simplicity when the time comes to update
      the plan.
    • When the merchant changes the dollar amount to be charged or the timing of the charges all associated cardholders are affected immediately.
  1. Modifiable Recurring Billing
    • Using the Batch Upload feature, the merchant can create an excel spreadsheet, .CSV or .TXT file to be uploaded as often as needed.
    • This feature provides the merchant with the simplicity of recurring billing
      and the ability to change any related billing information including the
      dollar amount.
    • If the merchant elects to create an excel worksheet, the template can
      be saved within the gateway and used for subsequent processing
      and settlement.
    • The Batch Upload process can process 50,000 transactions within approximately 90 minutes.

Yes No

How to edit established recurring billing for a single cardholder or a checking account

Step 1: Click add subscription from the main menu under recurring

Step 2:Select credit card or electronic check as the type of recurring transaction to continue

Step 3:Enter customer information for credit card or electronic check. Click continue to proceed.

Step 4:Select an existing plan from the plan namedrop down list or create a new billing plan by clicking on the click here link.These steps are the same for credit cards and electronic checks.

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 5:Click save to complete.

Yes No

How to edit established recurring billing

Step 1: Click list subscriptions from the main menu under recurring

Option: Merchants can also search recurring transactions to find a subscription by entering information they need. Simply fill in the fields and click submit for search results.

Step 2:Click the blue customer name to edit. Click download transactions to save information from the recurring customer list. Information includes subscription details as well as individual client information.

Step 3:Edit customer information. Merchant has the option to edit the customer’s billing plan from this menu. Click edit plan to change settings. Warning: all customers associated with the plan will be affected by your changes. Merchants can also delete the customer’s subscription by clicking the blue delete button at the top of the menu. Click save to complete.

Yes No

How to create billing plans for an unlimited number of cardholders or checking

Step 1: Click add plan from the main menu under recurring

Step 2:Enter information to create a new billing plan.Click saveto complete.

Yes No

How to edit billing

Step 1:Click list plans from the main menu under recurring

Step 2:Click plan name to modify information

Step 3:Edit any information to the existing billing plan. Warning: all customer associated with the plan will be affected by your changes. Existing plans can also be deleted by clicking the blue delete button at the top of the menu. Click saveto complete.

Yes No

How to create recurring billing with batch upload

Step 1: Click add plan from the main menu under recurring

Step 2: Click choose file to choose the file you wish to upload. Merchants can import a .CSV, .XLS or .TXT file for manually processing large amounts of transactions. Click upload batch to start processing.

Options:Two options are available for file format.

  1. Auto Detect File Format: batch program will auto detect file formats. For example $XX.XX as dollars. 14-16 digits as a credit card, etc.
  2. Use Selected Format: Merchants can add a new batch format by clicking “configure formats”. Batch templates can be saved for future use
Yes No

SwIPe-Overview

Yes No

SyncPay-Overview

QuickBooks SyncPay Guide

Yes No

How do I export transactions to Quickbooks™?

QuickBooks™ allows the user to select a date range of settled transactions and create an exportable .IIF file. This base QuickBooks™ file of settled transactions can then be imported into QuickBooks™.

Step 1:Click on Quickbooks™from the Main Menu

Step 2:Enter the date range of settled transactions and click submit

Step 3:Enter the Revenue Accounteither manually (this field are alphanumeric) or by using the Merchant Defined Fields


Note:there are 20 user definable fields available. Using the Merchant Defined Field will allow the merchant to refer to a specific revenue account for each transaction. This will enable the merchant to post to multiple Revenue Accounts. Select the Merchant Defined Field from the drop down list and the transactions will post to the designated accounts.

Step 4:Another option for the Deposit Account(this field are alphanumeric)

Step 5:Click Export to QuickBooks to save the file

Note:the saved file is ready to be imported to QuickBooks

Yes No

Gateway-Comparison-Chart

Yes No

VAS-Suite-Overview

Make This Document Your Own

Branding & Customization Instructions

Step 1. Replace the placeholder logo in the upper left hand corner of BOTH pages

  • Right click on the placeholder logo and select Change Picture, then navigate to your logo image you want to replace it with and insert it.
  • Note:Be sure to do this for both pages

Step 2. Change the color of the icons (skip this step if you are happy with the current icon colors used)

  • If you haven’t already done so, follow the instructions in the VAS Icon Sets Overview, which can be downloaded here.
  • Right click on an icon and select Change Picture, then navigate to the icon you saved with the color you want and insert it.

Step 3. Change font colors (skip this step if you are happy with the current font colors used)

  • Click on the text you want to change and highlight it.
  • With the text highlighted, navigate to the Font Color icon in your tool bar and select one of the colors shown, or follow the same steps used in the VAS Icon Sets Overview to customize the color of your font.

Step 4. Change the color of the colored rectangles (skip this step if you are happy with the current icon colors used)

Right click on the rectangle you want to change and select Format Shape

  • Icon Sets Overview to customize the color of your font.

Note: if you followed these steps for the font colors, it

Step 5. Remove this instruction page & save the document (Note: read this whole section before following instructions)

  • Click somewhere on this page and then navigate to Insert on your Word menu and select Remove Page.
  • To save, navigate to File on your Word Menu and select Save As,then rename your file to whatever suits your needs.
  • Note: You will probably want to save 2 versions of this file:
    • A PDF file to share with your merchants.
    • A Word doc for your own reference and for any future edits you may need to make.
Yes No

Data Security & Fraud Detection

Yes No

Payment Types & Acceptance Methods

Yes No

Back Office Tools

Yes No

Two-Factor-Auth-Overview

How it Works

  • The Two-Factor Authentication option will be managed through a new gateway user permission
  • To enroll, simply login to the admin account and click Options, then User Accounts
  • After selecting the username to be activated, you will see a checkbox to Require Two-Factor Authentication
  • After selecting the box, a security passphrase will be generated or you have the option to create a new Hex It is strongly recommended that you use the randomly generated key upon activation
  • Once the permission has been activated you will then need the passphrase to be input into an external application
  • After Two-Factor Authentication has been set up and synced in both systems, you will have to generate a key upon logging in. Each key generated on your device will remain active for 90 seconds whether or not they were used to grant access

Get the App: OATH Token for Apple Devices & Mobile-OTP for Android Devices

Yes No

Virtual Terminal

Virtual Terminal Guide

Customization

Required fields and adding/deleting fields.

Step 1:Merchants can add or delete non-required fields by click the gear.

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 2:Additional fields are pulled up. Toggle the fields on or off by clicking the boxed X. Click the disk to save changes.

Step 3:Note that there are up to 20 merchant definable fields available for the virtual terminal. The fields are cascaded through the virtual terminal and reporting functions (options, merchant defined fields).

Yes No

Recurring Billing

Establish recurring billing for a single cardholder or create billing plans that enable the merchant to manage an unlimited number of card holders per plan for checking accounts or credit card.

Step 1:Select the type of recurring transaction

Step 2:Recurring billing plan creation settings. The gateway can notify the merchant with credit cards that will expire in the next 30 days on the first of each month.

Yes No

Batch Upload

Merchant can import a .CSV, .XLS or .TXT file for manually processing large amounts of transactions. The program will create 16 parallel threads that will simultaneously process transactions (50,000 transactions can be processed within 90 minutes).

Features

Batch program will provide auto-detection of file formats. Ex: $XX.XX as dollars, 14-16 digits as a credit card, etc. Batch formats can be saved for future use.

Yes No

Gateway Options

Various options that make Virtual Terminal customizable for your needs.

Gateway Options Main Menu

Merchant Defined Fields

There are 20 merchant defined fields available for use. These fields will cascade into reporting sort and search options.

AVS Settings

Bankcard processors implemented the Address Verification Service to aid merchants in the detection of suspicious transaction activity.

CVV Settings

This is a system that matches the credit card number with a 3-digit security code that appears on the back of the credit card.

User Accounts

Create and manage sub-users with customer permissions and notification levels.

Load Balancing (ATRI)

Patent pending intelligent transaction routing from a single merchant to multiple processors. Ex: merchant requires $100,000 per month. Processor A will only approve $50,000. Two additional processors can be added, B and C for $25,000 each. Transactions will be intelligently routed by dollar amount, product or percentage.

Yes No

Reports

Extensive report search and mining capabilities.

Search Transactions

For specific transactions by any of the default or merchant defined fields.

Transaction Snapshot

Hover over calendar icon to select ranges

Transaction Snapshot

This week’s transaction summary snapshot is presented. Click on the magnifying glass to continue specifying the report results.

Sort Options

Results re-sort by credit card type.

Mining Feature

Select view these transactions.

Transaction Report

Transactions are presented in the Transaction Report. Click the blue ID to display the single transaction details.

Transaction Detail

When viewing the transaction details, the user can elect to email or print a receipt, void a non-settled transaction and authorize a new charge. Select sale and the merchant can charge this cardholder with a duplicate order to enter a new credit card and/or dollar amount to charge without having to obtain any additional information.

Yes No

Certify PCI™

CertifyPCI™ was designed specifically to streamline the PCI Certification process in an effort to help merchants easily achieve a higher level of security. It is an automated, web based process to PCI certify qualified merchants in minutes. $50,000 per occurrence Merchant Breach Insurance available, transparent product offering to your customers, assistance with Self Assessment Questionnaire (SAQ), Vulnerability Scanning including unlimited scans, downloadable PCI Certification Report.

New Merchants

New merchants will need to answer the Self Assessment Questionnaire to begin certification.

Returning Merchants

Retuning merchants will need to answer the Self Assessment Questionnaire yearly to maintain compliance.

QuickBooks™

  • Link allows the merchant to export gateway transactional information
    into QuickBooks™.

Integration

  • API documentation, shopping care references, Quickclick (shopping
    cart included with the gateway and programming examples).

iSpyFraud™

  • A rule-set based fraud management utility that allows merchants to
    configure extensive filters to help them in detecting fraud and screening suspicious transactions.
  • Extensive reporting system gives merchants a quick and easy way to review transactions, block suspicious activity and zero in on malicious users.
  • Looks at transactions both before and after processing and can decline transactions before and after authorization.
  • The successful implementation and reduction in chargebacks across numerous merchants has been a testament to the effectiveness of
    this product.
  • Example parameters are: 1. If a user charges credit card over [2] times for [Attempted] transactions, then [Deny Transaction]. 2. If daily [Attempted] transaction count for Credit Card exceeds [3], then [Flag for Review].

Easy-to-use Management Tools

  • iSpyFraud™ management tools give merchants quick and user-friendly control over their online fraud security system.
  • Control Panel allows merchants to maintain their own good and bad customer list, edit filters, restrict access by banning IPs and set up and maintain filter controls. Possible filtering criteria include but are not limited to: IP Address, Email Address, Transaction Count, Dollar Amount, IP Velocity check, Dollar Velocity check, Country, US/non-US IP Ban and much more.

Complete Protection

  • Properly set fraud filters eliminate the majority of fraudulent transactions
    in real time. The selected filters can be customized for each merchant,
    which are continuously updated to keep the merchant one step ahead
    of the fraudsters.
Yes No

Virtual Terminal Credit Card Guide

How to process a sale

A sale is a transaction that is authorized and captured for settlement. After a sale is processed, the transaction is automatically flagged to be settled.

A sale can be voided prior to settlement and must be refunded to reverse the transaction if the transaction has been settled.

Step 1:Click sale from the main menu under credit card

Step 2:Enter the sales details such as billing information, order information, card billing address, merchant defined fields and processor

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3:Click charge to complete

Transaction Successful

Transaction Failed/Declined

Transactions that do not process successfully will trigger a failure response.

Yes No

How to authorize or capture a transaction

Authorize is used to check if there is sufficient funds in the Credit Card inventory. When a transaction is authorized, it indicates that the Credit Card has adequate funds in the stock.

Capture is used when a transaction has been authorized and ready to be settled.

An authorization MUST be captured in order for the settlement to go through and the funds transferred. When a transaction is both authorized and captured, a sale is processed.

Step 1: Click authorize from the main menu under credit card

Step 2: Enter the details to authorize a transaction.

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Click authorize to complete

Transaction Successful

Step 1: Click capture from the main menu under credit card

Step 2: Enter the details to capture a transaction.

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Click capture to complete

Transaction Successful

Yes No

How to void a transaction

A void can be performed on a transaction prior to settlement. To void a transaction, simply enter the transaction ID in the void area under the Virtual Terminal section.

Step 1: Click void from the main menu under credit card

Step 2: Merchant can use magnifier icon to look up a transaction

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Enter the Transaction ID of the original transaction you wish to void. Click void to complete.

Transaction Successful

Yes No

How to process a refund

To refund a transaction, simply enter the Transaction ID and the amount you wish to refund.

Merchant can choose to make a full refund or a partial refund.

To make a partial refund, simply set the amount to be less than the original amount captured. To make a full refund, the amount must be equal to the original amount captured.

Step 1: Click refund from the main menu under credit card

Step 2: Merchant can use magnifier icon to look up a transaction

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Enter the Transaction ID of the original transaction you wish to void. Click void to complete.

Transaction Successful

Yes No

How to process a refund

To refund a transaction, simply enter the Transaction ID and the amount you wish to refund.

Merchant can choose to make a full refund or a partial refund.

To make a partial refund, simply set the amount to be less than the original amount captured. To make a full refund, the amount must be equal to the original amount captured.

Step 1: Click refund from the main menu under credit card

Step 2: Merchant can use magnifier icon to look up a transaction

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Enter the Transaction ID of the original transaction you wish to void. Click void to complete.

Transaction Successful

Yes No

Advanced features

Adding and deleting fields

Step 1:Merchants can add or delete non-required fields by clicking the gear.

Step 2:Additional fields are pulled up. Toggle the fields on or off by clicking the boxed X. Click the disk to save changes.

Yes No

Virtual Terminal Electronic Check Guide

How to process a sale

How to process a sale

An Electronic Check Sale is a transaction that is issued through an electronic check. The routing or ABA number and the account number printed on the check are used to process the transaction.

Step 1:Click sale from the main menu under electronic check.

Step 2:Enter the sales details such as billing information, order information, card billing address, merchant defined fields and processor

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3:Click submit to complete

Transaction Successful

Transaction Failed/Declined

Transactions that do not process successfully will trigger a failure response.

Yes No

How to process a sale

How to process a sale

An Electronic Check Sale is a transaction that is issued through an electronic check. The routing or ABA number and the account number printed on the check are used to process the transaction.

Step 1:Click sale from the main menu under electronic check.

Step 2:Enter the sales details such as billing information, order information, card billing address, merchant defined fields and processor

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3:Click submit to complete

Transaction Successful

Transaction Failed/Declined

Transactions that do not process successfully will trigger a failure response.

Yes No

How to void a transaction

A void can be performed on a transaction prior to settlement. To void a transaction, simply enter the transaction ID in the void area under the Virtual Terminal section.

Step 1: Click void from the main menu under electronic check

Step 2: Merchant can use magnifier icon to look up a transaction

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Enter the Transaction ID of the original transaction you wish to void. Click void to complete.

Transaction Successful

Yes No

How to process a refund

To refund a transaction, simply enter the Transaction ID and the amount you wish to refund.

Merchant can choose to make a full refund or a partial refund.

To make a partial refund, simply set the amount to be less than the original amount captured. To make a full refund, the amount must be equal to the original amount captured.

Step 1: Click refund from the main menu under electronic check

Step 2: Merchant can use magnifier icon to look up a transaction

Note: fields with red asterisk are required fields as set by the Affiliate.

Step 3: Enter the Transaction ID of the original transaction you wish to refund. Click refund to complete.

Transaction Successful

Yes No

Advanced features

Adding and deleting fields.

Step 1:Merchants can add or delete non-required fields by clicking the gear.

Step 2:Additional fields are pulled up. Toggle the fields on or off by clicking the boxed X. Click the disk to save changes.

Yes No
 

For inquiries contact us at (720) 277-0648