Set Up Credit Card ProcessingSet Up Credit Card Processing

The CCP tab is where you integrate iPoint to your credit card processing company. At this time we support four payment processors: TransNational, QuickBooks Payments, Authorize.net, and PayPal’s Payflow Pro.

Important: iPoint does not store any credit card information. We are simply a conduit to one of the four credit card processors. Customer credit card details are stored directly at those processors and we have no access to them through the iPoint software.

There are 2 ways a credit card can be charged through iPoint. The first is that one of your customers enters their credit card information on the web. The second is that a company employee enters the credit card information within iPoint.

  1. Your customer enters their credit card information on the web. – When the credit card information is entered it is only stored in the volatile memory on the machine it is entered in. When the user clicks to charge the credit card, the information is transmitted encrypted to one of our servers with https and then we send it to your payment processor to be charged. The payment processor gives us back a response and we store that response (this doesn’t have credit card information, but rather a confirmation number and if the charge was successful and stuff like that). At no time is the credit card information transmitted to the iPoint server you guys have. And at no point is the credit card information stored to a disk – it exists only as local memory which is then cleared.
  2. A company employee enters the credit card information directly into iPoint. – When the credit card information is entered it is stored in a Global field in FileMaker which is a field that only exists on that specific machine. The data never makes it back to your iPoint server. Then the process is the same where we send the information encrypted to our server which then sends it encrypted to your payment processor. We get a response back from the processor and store that and we clear the credit card information from the global field.

Credit Card Processor Details

From the Primary CC Processor dropdown, select which processer you will be using

Selecting the Primary CC Processor will change the details you need to enter.


TransNational

Preferred Vendor: TransNational is a preferred iPoint partner. They offer some of the most competitive credit card processing rates on the market today. TransNational also offers Point of Sale and remote hardware so that you can scan cards using magnetic stripe or chip to further reduce your costs. “

TransNationalTransNational
  1. Enter your API Key from your TransNational dashboard.
  2. If you will be using Terminal devices (for stripes, chips, and PIN input) click the Define Terminals button
    Define Terminal Defices
  3. Click the New Terminal button
  4. Or, you can click the edit pencil to modify details of an existing terminal
    Edit Terminal
    1. Enter the Terminal ID – provided by TransNational
    2. Give the terminal a Friendly Name – so you can recognize it
    3. Decide if receipts need to be printed by the terminal
      • Customer Only – prints the customer’s receipt
      • Merchant Only – prints the receipt for your accounting office
      • Both – prints both
    4. Signature Required – a check here forces signatures to be captured on the terminal. Note: This requires a special terminal mode from TransNational.
    5. Click Save
  5. Now, click the Select Company Default button to select a default terminal to use when a specific terminal hasn’t been chosen for a site or transaction.
    Default Terminal
  6. The default terminal details are now displayed in the Company Default Terminal ID

Terminal button
Setting up a TransNational terminal adds a new button to payment transaction windows. When processing credit card payments you will be able to select the terminal you are using to capture the credit card payment.

When your company has multiple sites you can set up default credit card terminals for each Site. This is done in Settings > Module Settings > Items

Terminal Setup

Here are a few notes regarding setting up TransNational terminals for use with iPoint:

  • Use a 2.4Ghz WiFi (5Ghz does not work well)
  • Enable WiFi Security and use the WPA/WPK2 protocol (gotta keep those transactions secure)
  • Ensure your WiFi network name contains letters and numbers only. Please, no special characters in the network name ($%&*) (even though we know how cool they are)
  • Set ports 7777, 5555, and 80 to allow Bi-directional traffic. These ports should not be blocked or forwarded
  • T-Mobile hotspots are not compatible with the TransNational terminals (unfortunately they are not TN-Mobile)

Authorize.netAuthorize.net

Authorize.net

You will need two pieces of information

  1. API Login and Transaction Key – once entered and committed, you are ready to go
  2. You can access this information by clicking the ? button
  3. The Sandbox/Demo checkbox allows you to process test transactions that will not affect your bank account. It is important to leave this unchecked once your credit card processing is working properly.
    • Note: Using the sandbox requires separate sandbox credentials obtained from your credit card processor. The same credentials won’t work with both sandbox and live accounts.
  4. Once your credentials have been entered, use the Test Connection button to verify that everything is set up correctly.

QuickBooks PaymentsQuickBooks Payments

QuickBooks Payments

You will notice two tabs on this tab.

  • OAuth 1.0a – this is a legacy connection to QuickBooks that is being depreciated on December 17, 2019. If you are still using OAuth 1.0a, you will need to move to OAuth 2 immediately.
  • OAuth 2 – this is the tab you want to use to connect to QuickBooks Payments.
  1. Go to iPoint Settings > Module Settings > Beta and check the QB OAuth 2 Enabled checkbox.
  2. Next, open a web browser and log into your QuickBooks Payments. This enables iPoint and Intuit to make the initial handshake necessary to get your credentials.
  3. Back in iPoint, click the QB Connect button. QuickBooks Connect button
  4. iPoint will open an authorization window where Intuit will confirm that you do indeed want to authorize this connection.
  5. Answer Yes to allow iPoint and QuickBooks Payments to connect.
  6. Back on the CCP integration tab, you will see several fields automatically populate with your QuickBooks credentials
    • QB Realm ID – this is your unique QuickBooks company identification number.
    • QBP2 Access Token and QBP2 Refresh Token – these are the unique license keys that QuickBooks grants to iPoint so that the two applications can communicate.
    • QBP2 Token TS – this is your merchant token with QBP.
    • QBP Enabled – this tells iPoint you are using QuickBooks Payments for credit card processing.
  7. Once these numbers have been entered by QBO, you are able to sync transactions and data to and from QuickBooks.

Some companies use a test “sandbox” QuickBooks account to test functionality. This is not necessary, but in the event you do have a sandbox account, you will first need to check the Sandbox/Demo checkbox to ensure iPoint is not syncing to your live QuickBooks Payments file.


PayPal Payflow ProPayPal Payflow Pro

PayPal Payflow Pro

Enter the following information from your PayPal Payflow Pro account

  1. User and Password – the credentials used to login to your Payflow Pro
  2. Partner – this is typically PayPal but can be adjusted here if your Payflow Pro account is managed by another payment partner.
  3. The Sandbox/Demo checkbox allows you to process test transactions that will not affect your bank account. It is important to leave this unchecked once your credit card processing is working properly.
    • Note: Using the sandbox requires separate sandbox credentials obtained from your credit card processor. The same credentials won’t work with both sandbox and live accounts.

Processing Credit Card Payments in iPoint

Processing credit card transactions is done in

Integration Disclaimer: Authorize.net, QuickBooks Payments, PayPal’s Payflo Pro, and TransNational are third-party applications that are completely unrelated to iPoint, LLC and we have no control over their code. From time to time, these companies may choose to modify their API code, which is outside iPoint’s control. We make every effort to maintain accurate connections to external, third-party applications. But in the event you have a problem, please let us know so we can work with them to rectify the situation.


On the right side of the Credit Card Processing portal are three tabs where you can define several additional options.

Pay Now & Receipt MessagesPay Now & Receipt Messages

Messages

On the right side of the Credit Card Processing window are a few settings that affect how customer notifications appear.

  • Reply To – When the email is sent through the online portal, the Reply Address will be either:
    • Sales Rep 1 – as listed on the invoice
    • Custom – selecting custom allows you to define both a custom email address where you want the reply to go. You might make this an accounting office or sales manager’s email address. Remember, this is a global setting for all pay now & receipt messages.
  • CC or BCC – checking one of these boxes will send a copy of the email to the individual who is logged into iPoint and processing the credit card requests.
  • Do NOT include PDF – by default, a PDF of the invoice or payment receipt is attached to the email iPoint generates. Checking this box will exclude that PDF as an email attachment. Keep in mind that the PDF will still be available on the Portal web page where the customer goes to pay their invoice.
  • Payment Page You have two fields where you can customize the messages a customer will receive on
    • Payment Success – Type the message your customer sees when the payment has been processed successfully through your payment processor.
    • Payment Failure – This message appears when a credit card payment fails through your credit card processor. This is the message your customer will see.

.
.
.
.
.
.

Credit Card Processing SettingsCredit Card Processing Settings

Settings

CCP: Accept Only CC ACH – Choose one option to force Credit Card Processing requests to only accept Credit Cards (CC) or eChecks (ACH). The default is to accept both payment methods. To clear a previous selection, click the Clear button.
CCP: Default To: CC ACH – This option sets the default choice in iPoint to accept Credit Cards (CC) or eChecks (ACH). This setting only affects payments entered directly into iPoint and does not affect the web payment portal.

CCP: Max $ for CC’s – this option will limit credit card payments to a specific dollar amount. Enter the maximum amount you’ll accept for a credit card payment in the box.
CCP: Max $ for ACH – this option will limit eCheck payments to a specific dollar amount. Enter the maximum amount you’ll accept in payment by Check.

.
.
.
.
.
.


Log

As you process credit card transactions, the log will capture errors and comments from your credit card processor. Your friendly iPoint Support Staff will use this information to help troubleshoot problems as they occur.

TransNational Errors

The standard TransNational processing errors will fall in the following number sequences:

  • 110: Transaction was successfully approved, but for a lesser amount
  • 200 – 299: Transaction has been declined by the issuer for various reasons
  • 300 – 399: Platform decline for configuration or fraud reasons
  • 400 – 499: Transaction error returned by the processor

A more detailed list of error codes and segments are available here:

QuickBooks Payments Errors

QuickBooks Payments lumps its error codes into the following six categories.

  • PMT-1000 through PMT-1999 – Fraud Warnings: There is something wrong with the credit card number, the card expiration date, or the CVC code for the card referenced.
  • PMT-2000 through PMT-2999 – Fraud Errors: The transaction was canceled because of a warning from the merchant’s fraud detection.
  • PMT-3000 through PMT-3999 – Account Errors: The request could not be successfully completed due to an account error.
  • PMT-4000 through PMT-4999 – Invalid Request: There was a problem with the connection between QuickBooks Payments and iPoint.
  • PMT-5000 through PMT-5999 – Transaction Decline – The merchant processor declined the transaction.
  • PMT-6000 through PMT-6999 – System Error – There was a temporary system error that should be resolved shortly. Try again in a few hours.

Specific QuickBooks Payments error code descriptions:

Authorize.net Errors

There are over 500 error codes that you might receive on Authorize.net transactions.

The best solution for understanding Authorize.net errors is to:

  1. Open the error response list as published by Authorize.net
  2. In the newly opened browser window, perform a Find (Ctrl+F) and enter the error code
  3. Read the text associated with the found code to get specifics about the error.
iPoint Version: 10.0516
Last modified: 28 May 2021

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.