Table of Contents

Setting up Bank Account & Credit Card Processors

Mitchell Paul-Soumis Updated by Mitchell Paul-Soumis

Read Time: 6 mins

Setting up Payment Processors

If you have not already set up a payment processor, start this process immediately as it requires some lead time to complete.

In order to begin receiving customer payments (and adding the appropriate customer payment methods) your first step in the process is adding in your preferred payment processors. Below you'll find a list of Payment processors supported by Sonar, as well as a list of items required to configure the processor.

All supported processors listed here utilize tokenization with Sonar. This means raw customer payment data never gets stored on your Sonar instance.

All available Payment Processors are configured from the same page - within your instance, navigate to Settings, followed by expanding the Billing segment, and lastly select either Bank Account Processor or Credit Card Processor, depending on which one you'll actively be creating.

In the tables for both Bank Account Processors and Credit Card Processors, you'll see a column labeled Primary. This column shows which processor is the default used to tokenize payment methods. There can only be one primary per instance. With additional processors added to an instance, the Sonar Support Team is able to import the tokens to continue working with that processor until the tokens expire and/or a customer re-adds their payment method, at which point the primary payment processor would be used moving forward.

Using Sonar to process your customer refunds directly is not available for all payment processors. Please confirm with your payment provider and the Sonar Support team if you have any questions.

e-Check/Bank Account Processors

You can access the Bank Account Processors by following these steps:

  1. Click on Settings
  2. Expand the Billing segment
  3. Click on Bank Account Processors

Next, click on the "Create Bank Account Processor" button to view the supported processors. In Sonar, we currently support the following Bank Account Payment Processors, highlighted in the image and table below:

  1. Provider Name

    Required Fields

    Special Requirements

    Authorize | https://www.authorize.net/

    • Login ID
    • Transaction Key
    To obtain the Authorize.net Transaction key, follow these steps:

    1. Select Settings under Account from the main menu on the left
    2. Click API Login ID and Transaction Key in the Security Settings section
    3. Enter the secret answer to the secret question you configured when you set up your account
    1. Have someone with edit permissions login to the Authorize Settings Portal
    2. Go to "Tools"
    3. Select the "Fraud Detection Suite"
    4. Select "IP Velocity Filter"
    5. Add 52.158.209.86 to IP Address Exclusion

  2. Provider Name

    Required Fields

    Bluepay

    • Account ID
    • Secret Key

  3. Provider Name

    Required Fields

    CardConnect | https://cardconnect.com/

    • Username
    • Password
    • Merchant ID

  4. Provider Name

    Required Fields

    Special Requirements

    IPPay | https://www.ippay.com/

    • Terminal ID
    Click here to download a PDF list of areas that IPPay currently offers processing, as of July 2019

    You have to contact IP Pay to get them to associate the Sonar egress V2 IP address of 52.158.209.86 with your Terminal ID. You will need to send an email like this to support@ippay.com:

    Please add the IP address 52.158.209.86 to the whitelist for TID XXXXXXXX.

  5. Provider Name

    Required Fields

    Propay ProtectPay | https://epay.propay.com/protectpay/

    • Account ID
    • Auth Token
    • Account Number

ACH

While ACH is also functionally a Bank Account processor, the methods by which ACH processors handle transactions differ sufficiently to be its own category. For more information on how ACH functions, take a look at our ACH Batching: Overview article.

In Sonar, we support any bank as long as they are using one of the following ACH formats:

  1. Provider Name

    Required Fields

    NACHA ACH

    • Bank Account Number
    • Company Description
    • Company Identification
    • Company Name
    • Immediate Destination
    • Immediate Destination Name
    • Immediate Origin
    • Origin Name
Chase Bank has specific field requirements that include adding trailing zeros to the company header. For more information on these requirements, please see the following:
NACHA File Requirements
Sample NACHA Formatted File.pdf
To assist with setting up a Canadian ACH provider, review the following article.

  1. Provider Name

    Required Fields

    Canada 1464 Byte EFT/CPA 005

    • Bank Account Number
    • Company Name
    • Data Center Code
    • Institution ID
    • Originator ID
Canada 1464 Byte EFT/CPA 005 requires adding the institution number using 8–9 characters for proper completion.

  1. Provider Name

    Required Fields

    Central 1 ACH Standard

    • Bank Account Number
    • Company Name
    • Data Center Code
    • Institution ID
    • Originator ID

  2. Provider Name

    Required Fields

    Royal Bank of Canada 1464 byte EFT

    • Bank Account Number
    • Company Name
    • Data Center Code
    • Institution ID
    • Originator ID

  3. Provider Name

    Required Fields

    BMO Harris Canada 80 Byte EFT

    • Bank Account Number
    • Company Name
    • Data Center Code
    • Institution ID
    • Originator ID

Credit Card Types

Adding a Credit Card Payment Processor can be done by following the below steps:

  1. Click on Settings
  2. Expand the Billing segment
  3. Click on Credit Card Processors

Within Sonar's Credit Card Processor configuration, you can configure each processor with a set of Credit Card Types. All supported Credit Card Types are listed below:

Details
1. Mastercard
2. Amex
3. Diner's Club
4. Discover
5. Maestro
6. Dankort
7. Union Pay
8. Visa Electron
9. Forbrugsforeningen
10. Visa
11. JCB

Credit Card Processors

Below is a list of supported Credit Card Payment gateways, as well as the information which can be entered to configure the gateway.

  1. Provider Name

    Required Fields

    Special Requirements

    Authorize | https://www.authorize.net/

    • Login ID
    • Transaction Key
    • Validation Mode
    To obtain the Authorize.net Transaction key, follow these steps:

    1. Select Settings under Account from the main menu on the left
    2. Click API Login ID and Transaction Key in the Security Settings section
    3. Enter the secret answer to the secret question you configured when you set up your account

    Expand here for a look at the different Validation Modes

    The Validation Mode field is used to indicate the processing mode for the payment. There are 3 different Validation Modes that can be selected:

    Live Mode: If selected, a $0 or $0.01 (depending on card type and processor) live transaction is processed against the card and then immediately voided. Address is required for cards that support $0 authorizations and will be validated along with card code, if submitted.

    Test Mode:     If selected, the card data is validated using simple mathematical checks to confirm that it appears to be valid. It is not a guarantee that the card is legitimate and the customer data is not validated.

    None:     If selected, no validation is performed at all. It is recommended that this option only be used for integration testing and not for production.

    1. Have someone with edit permissions login to the Authorize Settings Portal
    2. Go to "Tools"
    3. Select the "Fraud Detection Suite"
    4. Select "IP Velocity Filter"
    5. Add 52.158.209.86 to IP Address Exclusion

  2. Provider Name

    Required Fields

    Bambora | https://www.bambora.com/en/ca/

    • Merchant ID
    • Payment Profile API Key
    • Transaction API Key

  3. Provider Name

    Required Fields

    Bluepay

    • Account ID
    • Secret Key

  4. Provider Name

    Required Fields

    CardConnect | https://cardconnect.com/

    • Username
    • Password
    • Merchant ID

  5. Provider Name

    Required Fields

    Special Requirements

    IPPay | https://www.ippay.com/

    • Terminal ID
    Click here to download a PDF list of areas that IPPay currently offers processing, as of July 2019

    Either Contact IP Pay to get them to associate the Sonar egress V2 IP address of 52.158.209.86 with your Terminal ID. You will need to send an email like this to support@ippay.com:

    Please add the IP address 52.158.209.86 to the whitelist for TID XXXXXXXX.

  6. Provider Name

    Required Fields

    Moneris Canada eSelect Vault |

    https://www.moneris.com/en/Products-Services/Online/Ecommerce

    • Store ID
    • API Token

  7. Provider Name

    Required Fields

    PayGate PayHost/PayVault | https://www.paygate.co.za/integration/payhost/

    • ID
    • Password

  8. Provider Name

    Required Fields

    Propay ProtectPay | https://epay.propay.com/protectpay/

    • Account ID
    • Auth Token

  9. Provider Name

    Required Fields

    Stripe | https://stripe.com/en-ca

    • Secret Key

You can contact any of these companies directly for exact terms and pricing details.

How did we do?

Billing Settings

Contact