How To - Payments (Cash, Check, Credit Card, and ECheck)

Summary

Customer payments can be set up to be paid via:

  • Cash  (Note - You can use this payment designation in Orion to enter a credit card or echeck payment if you are processing those payments directly through your gateway)
  • Check
  • Credit Card Processor (customer information is stored on Orion)
  • Credit Card Token Processor (customer information is stored  at the Token gateway)
  • ECheck Processor (ACH or eCheck)

 

ECheck Component Information

The ECheck component allows your website to securely process electronic checks without the need to redirect to a third-party site.  All transactions are accomplished through a secure HTTPS Post to any supported gateway. The secure response is received and then stored in the component’s response properties. Any web site on a standard HTTP server or any standalone application can process transactions without the need for a secure server or third-party intervention.

  • Select one of the gateways supported by the ECheck component and then set up an account with that gateway vendor. Once you have an account set up with a valid login Id and password, you can use the ECheck component.  .
  • Set the Gateway property in Orion to the gateway you wish to use. If this gateway supports an alternate URL to send test transactions to, set the Gateway URL at this time.
  • Next, set the Merchant Login (and for some gateways the Merchant Password). These are supplied by your gateway vendor when you set up an account.

Now you are ready to process transactions. Not all gateways process ACH or ECheck transactions the same way. While all gateways require a bank routing and account number, some require additional information such as a driver’s license number, bank name, or the account type (checking or savings). Check with the gateway for their requirements.

Processor Gateways

Orion integrates with a significant number of processing vendors.

Select a card processor gateway from the Credit Card Gateway List and/or the ECheck (ACH) Gateway List,   Some gateways handle both credit cards and ACH transactions.  Check to see which gateways appear on both lists.

Credit Card Gateway List

ECheck (ACH) Gateway List

Electronic Payment Setups

All of the following items need set up in order to process electronic payments through Orion:

  • Card Processors - all gateways need to be set up here
  • Card Types - all credit cards you will be accepting as payment
  • Credit Card Token Processors - all gateways where customer credit card payments are processed and customer data is stored
  • ECheck Processors - all gateways where customer ACH and ECheck payments are processed and customer data is stored on Orion
  • ECheck Token Processors - all gateways where customer ACH  and ECheck payments are processed and customer data is stored
  • Payment Types -  ONLY token card processors require association with a payment type
Electronic Payment Setups

Card Processor Setup

Go to your Owner (Partner) account:

  1. Select Setup tab
  2. Under the Accounting section, select one of the following:
    • Card Processors - gateways for processing credit cards, BUT storing the customer credit card information on Orion
    • Credit Card Token Processors - gateways for processing credit cards, AND storing customer credit card information with the gateway
    • ECheck Processors - gateways for processing electronic checks , BUT storing the customer bank account information on Orion
    • ECheck Token Processors - gateways for processing electronic checks, AND storing customer bank account information with the gateway

Note:  You will either use the Regular processors or the Token processors

  1. Click Add

Required fields are in RED

  1. Enter the Name (Same as Card Gateway is good, Enter the Card Gateway from the drop-down list
  2. Enter your Merchant Login and Merchant Password
  3. Enter your credit card processor’s Gateway URL  (Note: There may be an alternate URL to send test transactions)
  4. Enter any other configuration specific to your processor (if Tier sync or multiple branded owners is in use, select any existing configuration options that are in place for the same card processor on the other owner)
  5. Select Save to save the Card Token Processor, or Save/New to save and create another.

Credit Card Processors

Go to your Owner (Partner) account:

  1. Select Setup tab
  2. Under the Accounting section, click Credit Card Processors
  1. Click Add

Required fields are in RED

  1. Enter the Name (Same as Card Gateway is good,
  2. Enter the Card Gateway from the drop-down list
  3. Enter your Merchant Login and Merchant Password
  4. Enter your credit card processor’s Gateway URL  (Note: There may be an alternate URL to send test transactions, check with your gateway service provider)
  5. Enter any other configuration specific to your processor
  6. Select Save to save the Card Token Processor, or Save/New to save and enter another gateway service provider.

Token Credit Card Processors

The steps are the same as adding a Credit Card Processor (without Token), but the information input is somewhat different:

From your Partner Account

  • Select the Setup tab
  • Select  Credit Card Token Processors

 

  • Select the Add button

Populate the fields presented (required fields are in red)

  • Name - this can be any value you wish to give to the Card Processor.  It just an identifier.  Although, not a usual practice, If you are using both regular credit card processors and token credit card processors, you will want to add the wording "Token Credit Card" to the name
  • Select any gateway – as this is not used during token processing
  • Merchant Login – enter your merchant account username, login or ID information supplied by your Gateway
  • Merchant Password – enter you merchant account password supplied by your Gateway
  • Test Mode – if selected, will allow you to run test Bill Run processing simulations on your accounts before going live. All Credit Cards whether real or fake will receive a successful response when using this check box. This should be used if you simply want to confirm that billing is attempting to process cards and should NOT be used in a production system scenario
  • Gateway URL – allows you to override the Gateway URL. This can also be used to post to a test gateway
  • Attribute – allows you to specify additional attributes specific to the gateway.
  • Configuration – allows you to enter uncommon configuration settings for the gateway
  • Threshold Amount – enter a threshold value that will prevent credit card charges if the payment amount is less than the threshold value
  • Select Save to save the Card Token Processor, or Save/New to save to processor and create another

 

  • Select the Add button

ECheck Processors

The ECheck component allows you to use multiple Internet Payment Gateways through one interface and one component. This allows for easy migration from one gateway to another, as well as quick integration into applications or web services.

The ECheck component allows your website to securely process electronic checks without the need to redirect to a third-party site. All transactions are accomplished through a secure HTTPS Post to any supported gateway. The secure response is received and then stored in the component’s response properties. Any web site on a standard HTTP server or any stand-alone application can process transactions without the need for a secure server or third-party intervention.

Go to your Owner (Partner) account:

  1. Select Setup tab
  2. Under the Accounting section, click ECheck Processors

•Select the Add button

Required fields are in red

Populate the fields presented:

  • Name - this can be any value you wish to give to the ECheck Processor.  It just an identifier.  
  • E Check Gateway – select the appropriate gateway from the drop-down menu
  • Merchant Login – enter your merchant account username, login or ID information supplied by your Gateway
  • Merchant Password – enter you merchant account password supplied by your Gateway
  • Test Mode – if selected, will allow you to run test Bill Run processing simulations on your accounts before going live. All Credit Cards whether real or fake will receive a successful response when using this check box. This should be used if you simply want to confirm that billing is attempting to process cards and should NOT be used in a production system scenario
  • Gateway URL – allows you to override the Gateway URL. This can also be used to post to a test gateway
  • Attribute – allows you to specify additional attributes specific to the gateway.
  • Configuration – allows you to enter uncommon configuration settings for the gateway
  • Threshold Amount – enter a threshold value that will prevent credit card charges if the payment amount is less than the threshold value
  • Select Save to save the Card Token Processor, or Save/New to save to processor and create another

ECheck Token Processors

The steps are the same as adding a Credit Card Token Processor (without Token), but the information input is somewhat different:

From your Partner Account

  • Select the Setup tab
  • Select  Credit Card Token Processors

 

  • Select the Add button

Populate the fields presented (required fields are in red)

  • Name - this can be any value you wish to give to the Card Processor.  It just an identifier.  Although, not a usual practice, If you are using both regular ECheck Processor and ECheck token processor, you will want to add the wording "TokenECheck" to the name
  • E Check Token Gateway – select the gateway from the drop-down menu
  • Merchant Login – enter your merchant account username, login or ID information supplied by your Gateway
  • Merchant Password – enter you merchant account password supplied by your Gateway
  • Test Mode – if selected, will allow you to run test Bill Run processing simulations on your accounts before going live. All Credit Cards whether real or fake will receive a successful response when using this check box. This should be used if you simply want to confirm that billing is attempting to process cards and should NOT be used in a production system scenario
  • Gateway URL – allows you to override the Gateway URL. This can also be used to post to a test gateway
  • Attribute – allows you to specify additional attributes specific to the gateway.
  • Configuration – allows you to enter uncommon configuration settings for the gateway
  • Threshold Amount – enter a threshold value that will prevent credit card charges if the payment amount is less than the threshold value
  • Select Save to save the Card Token Processor, or Save/New to save to processor and create another

 

Payment Types

Go to your Owner (Partner) account:

  1. Select Setup tab
  2. Under the Accounting section, click Payment Types
Payment Types

Select Add

Select from the drop-down menu,either Cash, Check or Credit Card, set up was shown below

If you are using E Check Processor, E Check Token Processor or Credit Card Token Processor, you will need to select that processor from the drop-down menu for the correct processor.

If you are using just a Credit Card Processor (no token), no processor detail is required.

Required fields are in RED

Set up all payment types you’ll be using.

  • Name - Same as Payment Type, except for "Cash" type, which is "Other"  and "Check" which is ACH (see above example)
  • Payment Type - Select from drop-down menu
  • Disbursement Type - Automatic
  • General Ledger – select the General Ledger (optional) to associate with the payment type
  • Payment Code – select the Payment Code (optional) to associate with the payment type (for instance ‘Online Payment’)
  • E Check Processor – for Check payment type only, if using a auto withdrawal method
  • E Check Token Processor – for ECheck Token payment type, select the correct E Check Token Payment processor
  • Credit Card Token Processor – for Credit Card payment type; select the correct Credit Card Token Processor
  • Default Detail Message – message that can be used if the payment details field is left empty by the user on the Add Payment page
  • Select Save or if you need to enter more than one Payment Type, select Save/New

Process a Credit Card to test if the configuration is in order (see the Processing Credit Cards section below)

Card Types

Go to your Owner (Partner) account:

  1. Select Setup tab
  2. Under the Accounting section, click Card Types
  1. Click Add

Required fields are in RED

Set up all credit card types you’ll be processing.

  • Name - Credit Card Name, select from drop-down menu (i.e. Visa, Master Card, Amex).  
  • Card Processor - Enter the processor gateway name from the drop-down menu
  • AVS - this prompts EngageIP to actually send the data to the processor (Please note that some gateways may also support non-AVS transactions, where customer name and address data is not required. However, these transactions are risky and are not recommended for fraud reasons. When a transaction is authorized, the status of the response will be indicated by the TransactionApproved property. For more details as to why a transaction was authorized or declined, it is recommended that the developer check the ResponseCode and ResponseText properties. Please see the ResponseCode property for a list of specific response codes for each gateway).
  • Card Type - select from the drop-down list
  • Pre Auth Req - Optional
  • Pre Auth Amount Overridable - Optional
  • Pre Auth Default Amount - usually set at $1.00 for testing purposes
  • Select Save or if you need to enter more than one Payment Type, select Save/New

Card Test Mode

When testing the credit card processor on your system, there are two test modes available.

  1. On the processor page (Setup tab --> Card Processors --> Add/Edit).  As shown, there is a test mode check box. This is an Orion specific test mode, all cards whether real or fake will receive a successful response when using this check box. This is best used if you simply want to confirm that billing is attempting to process cards and should NOT be used in a production system scenario.

OR

  1. Set your processor gateway up in test mode (i.e. the test mode check box in Orion would NOT be checked). This configuration will be specific to each process and is not completed in Orion. You will need to login to your processors gateway directly and configure this. Please refer to your processor company documentation for the configuration and how to use the test mode in this scenario. When you are satisfied that credit cards are processing with this setup, simply login to the processor gateway and turn off test mode. In most cases the processor gateway test mode will be more robust then Orion allowing you to enter specific amounts to test a successful debit, or other amounts to test processing failures. (i.e. AuthorizeNet allows you to use 1 dollar for a success, and any other amount would return a failure, in this way you can confirm that success messages and failure messages and operations are working correctly).

When confirming that your processor is working, the best method is to set the processor gateway to test mode, process some cards and run billing on your development server to confirm credit cards are charging as expected.

A good way to test a live credit card processor is to setup a personal account with a real company credit card, and process a $0.10 transaction. This is a small dollar amount that is easy to test and if successful, any larger amount for other real credit cards will be successful.  This is an excellent method for quickly confirming the credit card process is functional

Sample Test Mode Setup

Sample Test Mode Setup

Sample Live Mode Setup

Simply uncheck the'Test Mode checkbox to configure live mode.

Customer Payment Method Setup

Go to either the Customer's Enterprise or the Customer's Customer account, to set up the customer's Payment Method.  Payments are posted on the account where the invoices reside.  This is usually the Enterprise account, but may reside on the Customer account.  When a customer has more than one location and they have requested that each location receive a separate invoice, the invoice will be found on the Customer's Customer account.  Check the invoice tab to see where the invoices reside).

  1. Select the Tools tab
  1. Select Payment Methods (Tools and Utilities column)
  1. Select Add and select from the drop-down menu  (Note:  Set up all possible payment methods)

Cash

You will use "Cash" if you are not processing your payments through Orion.

  • Select Cash, no further details required for set up.  Cash is used for payments that are being processed outside of Orion.

Check

Select Check from the drop-down menu

Required fields are in RED

Complete all information required by your credit card processing vendor.

Select Save or if you need to enter more than one Bank Account select Save/New

Credit Card

  1. Select Credit Card from the drop-down menu

Required fields are in RED

Complete all information required by your credit card processing vendor.

Select Save or if you need to enter more than one Credit Card, select Save/New

 

Default Payment Method Designation

Once your payment methods have been entered:

Place a check mark to the left of the payment you want to designate as Default

Select the Default button

The Default payment method will now appear in BOLD   (Note: In order for credit cards to be run in mass during or after a monthly bill run, the credit card to be charged must be the default payment method)

Deleting a Payment Method

  1. From the list of Payment Methods, put a check mark in the Select box next to the payment method.  Select the Tools tab
  2. Under Tools and Utilities, select Payment Methods
  3. Enter a checkmark to the left of the credit card you wish to delete
  4. Select the Delete button.  Note:  The default payment method will be in Bold.  Default payments cannot be deleted.  You must first assign a new default payment.
Deleting a Payment Method

Credit Card, Credit Card Token and ECheck Token Billing Rules

For credit cards to run as part of an automated bill run, they must be set as the default payment method (bolded under payment methods on Tools tab of an account)

Credit cards will be processed automatically if the customer's ‘Credit Card’ to be charged is checked and if on the Bill Run setup page, the ‘Enabled’ check box is selected.

Credit Card Tokens or E Check Tokens will be processed if ‘Run E Check Token’ or ‘Run Credit Card Token’ are selected on the Bill Run setup page

Expired credit cards are not attempted when processed through the Bill Run.

Canceled accounts will NOT be attempted during a credit card bill run.

Troubleshooting

Below provides some common errors when attempting to process cards. You can find errors by reviewing the following reports:

  1. Payment Decline: lists basic errors
  2. Event Log: shows Credit Card return messages and errors
  3. Payments: shows a full unparsed list of the returned value from the gateway

Credit Card / SSL (Secure Sockets Layer) Response Errors

Credit Card return messages and errors will show in the Orion event log and are common among all processors compatible with the iBiz processor module. Some of the most common errors are:

Credit Card Response Errors

159 Invalid form variable index (out of range).

501 Data field invalid length.

502 Data field invalid format.

503 Data field out of range.

504 Luhn digit check failed.

505 Card date invalid.

506 Card expired.

507 Card type unknown.

510 No gateway specified.

511 Invalid data entered.

512 Truncated response.

513 Invalid response.

514 A Special Field is required for this transaction type.

542 Error computing MD5 hash for Authorize.Net

SSL Response Errors

270 Cannot load specified security library.

271 Cannot open certificate store.

272 Cannot find specified certificate.

273 Cannot acquire security credentials.

274 Cannot find certificate chain.

275 Cannot verify certificate chain.

276 Error during handshake.

280 Error verifying certificate.

281 Could not find client certificate.

282 Could not find server certificate.

283 Error encrypting data.

284 Error decrypting data

Have more questions? Submit a request

Comments

Powered by Zendesk