Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Overview

Purpose

The purpose of the GoToBilling (GTB) SOAP Web Service is to provide an easy set methods for sending and receiving information from GTB in the form of SOAP requests. This allows you have a readily available platform integrating many current applications with GTB.

...

The MerchantAuth complex type allows for the delivery of the client credentials to authorize service requests.

MerchantAuth Fields

Field NameRequired (R); Optional (O); Conditional (C); Read Only (RO)Data Type & LengthDescription & Field Values
login
**DEPRECATED** login ROstringThis is the login identifier supplied by OmniFund.  This can be the six digit Merchant ID or the OAuth client_id.  Required if no access_token is supplied

**DEPRECATED** pin

ROstringThe associated gateway pin to the Merchant ID supplied in the 'login' field, or the associated client_secret associated with the client_id.  Required if no access_token is supplied
access_tokenOstringValid OAuth access token. 
access_keyO or CRstringProvide API access key pair parameters in lieu of standard MerchantAuth fields - CONDITIONALLY  REQUIRED: if access_key parameter is supplied, access_secret parameter must also be supplied. For more information on obtaining an API access key, see: Managing API Access Keys
access_secretO or CRstringProvide API access key pair parameters in lieu of standard MerchantAuth fields - CONDITIONALLY  REQUIRED: if access_key parameter is supplied, access_secret parameter must also be supplied. For more information on obtaining an API access key, see: Managing API Access Keys
source_descriptionOstringDescription of the source originating the request.
module_descriptionOstringDescription of the module originating the request.

CustomerInfo

Customers or Customer Records are the individual people or companies that are customers to the Business(MID) we are working with. Typical customer data is Name, Address, Phone number etc. There are two unique fields in GTB that help identify customers. More will be explained below but one is a unique internal ID created by GTB called customer_id and the other one is created externally by the business called customer_name. The customer_name created by the business allows them to use a unique value from their accounting or other customer service systems so they can tie their data to the data in GTB.

CustomerInfo Fields

Field NameRequired (R); Optional (O); Conditional (C); Read Only (RO)Data Type & LengthDescription & Field Values
customer_idCString (50)A unique customer identifier set by GTB.
first_nameCString (50)Required if display_as='contact'
last_nameCString (50)Required if display_as='contact'
customer_nameRString (100)Externally defined unique field for each Customer. This is a free-form identifier that is created by the user to allow matching of customers by existing customer numbers in accounting or other customer databases and systems. This field MUST be unique in order for many other functions and features the customer may use.
display_asRString (50)Values: 'company' or 'contact'.

Defaults to contact if not recognized.

companyCString (50)Required if display_as='company'
address1OString (100)
address2OString (50)
cityOString (50)
stateOString (2)
zipOString (20)
phoneOString (50)
emailOString (100)
ssnOString (50)
dl_numberOString (20)
dl_stateOString (2)
notesOString
activeRBooleanDetermines whether a customer record is Active or Inactive. Inactive customers show as grayed out within the GTB application
  • 0 – Disabled (Inactive)
  • 1 – Enabled (Active)
hiddenOBooleanDetermines whether customer record is visible or not within the main GTB app. It’s the status field that is used when a customer record is deleted but in reality the we don’t delete the customer from the database, we just make it invisible to the user.
  • 0 – Hidden
  • 1 – Visible
date_addedROStringThe date the customer was originally added to GTB. YYYYMMDD format

...

AccountInfo Fields

Field NameRequired (R); Optional (O); Conditional (C); Read Only (RO)Data Type & LengthDescription & Field Values
account_idCIntA unique identifier assigned by GTB for every Account that is added to the system.
customer_idRIntUnique ID of the customer the account is being assigned to.
account_nameOString (100)This field allows a consumer to name their checking or credit card account to anything they want as an identifier for their account.
account_numberCString (100)

For credit cards it is the 16 digit card number and for Checking Accounts it is the routing and account number including all leading zeros.

routing_numberCString(9)ABA Routing number for bank account.
enabledOBooleanDefines whether this Account is enabled for adding transactions or not. If it is disabled, then no transactions can be done using this account within GTB.
  • 0 – disabled
  • 1 – enabled
typeRIntDefines the account type, i.e. credit card or ACH
  • 1 – Checking
  • 2 – Credit Card
bank_nameCString (50)If account type is ACH, indicates the name of the banking institution
cc_nameCString (100)Actual Name of the customer as it appears on their credit card.
expirationCStringCard expiration date. In the format: MMYY
cvvCString (4)The 3 or 4 digit card security value on the card. When retrieving information about an account the CVV value will always be masked for security reasons.
cc_zipCString (5)The 5 digit billing zip code associated with the card.
is_savingsCBooleanTells you if the Checking Account is a Savings account or not.
  • 0=no
  • 1=yes
date_addedROStringFormat: YYYYMMDD
date_modifiedROStringFormat:YYYYMMDD

...

CustomField Fields

Field NameRequired Optional Conditional Read Only (ROR);Data Type & LengthDescription & Field Values
idRIntThe unique identifier for the custom field as provided by GotoBilling.
valueRIntValue assigned to the custom field.

...