Compatible Credit Card Processing Gateways

Dispatch allows you to link your existing credit card processing account to Dispatch which will enable Technicians to take payment directly and immediately from customers. Additionally, some gateways also allow for ACH/Bank/eCheck payments that can be enabled enabled inside of our applications.

Each payment gateway is set up differently so the information we'll need from your specific gateway account varies. Please find the Gateway you're currently using and follow the instructions to finding the proper credentials.

NOTE: Once you've acquired your gateway credentials, please email support@dispatch.me to complete the activation process by providing the details mentioned below for your desired gateway.

Article Sections

  1. Clearent
  2. First Data | Payeezy
  3. Stripe
  4. Quickbooks Payments (temporarily unavailable)
  5. Authorize.Net
  6. Cayan
  7. Braintree

Clearent [Preferred]

Tired of monthly fees? Want to avoid unnecessary setup fees? We have you covered. 

Currently available is an opportunity for companies like yourself to participate in a partnership for taking electronic (Credit Card, Debit Card) payments. View all of your payment transactions and receive timely deposits to your bank account.

  • NO Monthly Fees
  • NO Setup Fees
  • Competitive Transaction Fees
  • Integrated with Dispatch

Register at https://signup.dispatch.me/credit-card-processing-application

First Data / Payeezy

Required Credentials: 

  1. "Terminal Password""Gateway ID"
Log into your First Data account using your username and password:  https://globalgatewaye4.firstdata.com/?lang=en
NOTE:The username and password are distinct from the Gateway ID and Terminal Password that you’ll receive at the end of this process. We do not require that you send us your username and password - you should keep that information private and not share it with anyone. If you do not know what your username and password are, please contact your First Data representative. If you need any assistance with this process please do not hesitate to ask.

After you log in, on the right hand side of the screen click on the link labelled “Terminals.”
Ensure “Terminals” is selected at the top and then click into the Terminal that you want to use (you may only have one showing in your view).
Once you select the terminal, a form should appear. You should do the following:
  1. Copy the Gateway ID and paste into the body of an email
  2. Click on “Generate” to see the password. Copy the password (this is your terminal password) and paste into body of email
  3. Click save

Stripe

Required Credentials: 

  1. "Secret API Key"
For Stripe integration setup we'll need your " Secret API Key". Your API keys are located in your stripe account settings.
If you do not see your API keys, this means that you have either Read & Write or Read Only access, and are not an administrator for the account.
You will need to get in touch with the administrator of your account for the API keys or to request that they make you an administrator in the account's  team settings.       

Quickbooks Payments (temporarily unavailable)

Collecting payments through Quickbooks requires a series of steps that will give you 4 critical pieces of information. These are time sensitive so once you've generated the credentials, send them to us in email to support@dispatch.me immediately.

Required Credentials: 

  1. Client ID
  2. Client Secret
  3. Refresh Token
  4. Access Token

To obtain the above details, you'll need to register an "App" within the developer marketplace. This is a requirement with Quickbooks in order to connect to Dispatch.

Steps

First, signup to the developer sign in at https://developer.intuit.com/app/developer/myapps. Once you're logged in use the 'Create an App' button.

There will be several fields to input - we'll walk you through each below. Don't worry, this is relatively straight forward!

Your screen will look something like the following and you'll want to choose QuickBooks Online and Payments.

Give the app a name - we suggest Dispatch Payments app in the "app name" field. And in the Select a Scope field, choose Payments. Then press the Create App button.

Next will be a few more fields that may seem confusing. Make sure you have Production select at the left and click on Keys & OAUTH. There are 4 sections that need to be filled out. In order 

In the Terms of Service links fields, put https://www.dispatch.me/privacy in BOTH fields.

The Target industries for this app options mostly do not apply - select Payments. And the next two fields can remain as All and Payments (US Only). 


Once you've completed all 4 sections, you'll be able to view a screen like the following. This is where you'll want to click on OAuth 2.0 Playground. You can also get to the right page at https://developer.intuit.com/app/developer/playground.

The next set of steps will generate the 4 necessary keys/tokens that must be sent to us in order to connect your Dispatch account. We suggest opening a draft email so you can copy and past the 4 necessary keys/tokens in order to send to support@dispatch.me 

IMPORTANT: 

We suggest only doing the following between 9am and 4pm Eastern Mon-Friday as it's a time-sensitive process.


Step 1.
Select the app you created and make sure it says (Production) in the name. Under the Scopes section, choose Payments and click Get authorization code.

You'll be taken to a screen to connect with your QuickBooks Online account. Choose your company from the list and click Next.

Only after you've done the above, copy both the Client ID and Client Secret. Be sure to copy the entire contents of the field and paste in to the draft email you created earlier.

Step 2.

These fields will likely be filled out. Simply click on Get Tokens to continue the process.

Step 3.

These fields will likely be filled out. Simply click on Submit charge.

Only after you've done the above, copy the Access token. Be sure to copy the entire contents of the field and paste in to the draft email you created earlier.

Step 4.

The last step is to click the Refresh Access Token.

Only after you've done the above, copy the  Refresh Token. Be sure to copy the entire contents of the field and paste in to the draft email you created earlier.

At this time you have about 60 minutes for us to connect your tokens to Dispatch. Please send the email to support@dispatch.me so you can get connected.


Authorize.Net 

Optional: ACH/eCheck processed can be enabled

Required Credentials: 

  1. "API Login ID"
  2. "Transaction Key"
To obtain the API Login ID and Transaction Key:
  1. Log into your Merchant Interface at https://account.authorize.net
  2. Click Account from the main toolbar
  3. Click Settings in the main left side menu
  4. Click API Login ID and Transaction Key in the Security Settings section
  5. Under Create New Transaction Key, enter your Secret Answer
  6. Note: When obtaining a new Transaction Key, you may choose to disable the old Transaction Key by clicking the box titled, Disable Old Transaction Key(s). You may want to do this if you suspect your previous Transaction Key is being used fraudulently
  7. Click Submit
If the Disable Old Transaction Key(s) box is not checked, the old transaction key will automatically expire in 24 hours. When the box is checked, the transaction key expires immediately. 

Cayan (Compatible)

Required Credentials: 

  1. "Site ID"
  2. "Key"
  3. "Name"
When you signed up with Cayan you should have received an email that included your  Site ID, Key, and  Name.  
If you did not receive that email, please contact Cayan directly at (800) 498-0823 and inform them that you need your Site ID, Name and Key for use with Spreedly/Dispatch.

Braintree 

Required Credentials: 

  1. "Merchant ID"
  2. "Public Key"
  3. "Private Key" 
Log in to the Braintee Control Panel
  1. Navigate to Your Username -> My User
  2. Click the blue link titled API Key
  3. If no API keys appear, click Generate New
  4. Click View under the Private Key column
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.