Billing APIs

Introduction
Billing API is a RESTful API that allows setting up customers, collecting payments and maintaining balances for these customers, as well as creating recurring billing subscriptions.

Billing API documentation includes the following sections:

Objects - lists all recurring billing objects. The purpose of this section is to describe all object fields, their format and usage, provide the links to the corresponding database tables.

Type Enumerations – lists possible values that can be used in the respective fields within Billing API requests and responses. The purpose of this section is to provide an explanation of all enumerations used for API calls.

Actions - lists all actions that can be performed with key recurring billing objects. The purpose of this section is to describe the methods and format of API requests and the format of responses.

Integration Notes – lists integration notes associated with the Billing API objects and actions. The purpose of this section is to provide explicit information about the peculiarities of specific actions and object fields.

Code samples - provides examples of recurring billing use cases (creating billing plans, subscriptions, freeing or canceling subscriptions, reversing transactions, etc) and their implementation in JSON, XML, XURL formats. The purpose of this section is to provide examples that can be used for testing of the integration with the gateway.

To learn how to work with the Billing API, we recommend reviewing the integration notes first. Key recurring billing module terms are available here.
For more detailed information about the recurring billing configurations and management, check the Recurring Billing Guide.


ProcessingInfo

Type:  
Abstract:  no
Status:  Active
Java Class:  ProcessingInfo
Information associated with transaction processing within internal and external systems.
id
References: Capture Info.Id
XML Representation: attribute
Attributes:
Default Value
Identifier of the object used for references; auto-incremented integer value.
createDate
References: Capture Info.Create Date
XML Representation: attribute
Attributes:
Default Value
Date when the record was created

In API request, the date must be submitted in yyyy-MM-dd format.
In API response, the date is returned in yyyy-MM-dd HH:mm:ss format.
holderName
References: Capture Info.Holder Name
XML Representation: attribute
Attributes:
Default Value
Name of bank account or credit card holder.

Name of a payment card or bank account holder. The value is a concatenation of the firstName and lastName field values separated by a space.
accountNumber
References: Capture Info.Account Number
XML Representation: attribute
Attributes:
Default Value
Encoded credit card number or bank account number.
accountAccessory
References: Capture Info.Accessory
XML Representation: attribute
Attributes:
Default Value
Expiration date of the card or bank routing number.
token
References: Capture Info.Token Code
XML Representation: attribute
Attributes:
Default Value
Token generated for the provided payment information.
street
References: Capture Info.Street
XML Representation: attribute
Attributes:
Default Value
Street mailing address of the cardholder.
city
References: Capture Info.City
XML Representation: attribute
Attributes:
Default Value
City mailing address of the cardholder.
state
References: Capture Info.State
XML Representation: attribute
Attributes:
Default Value
State mailing address of the cardholder.
zipCode
References: Capture Info.ZIP Code
XML Representation: attribute
Attributes:
Default Value
ZIP/postal code of mailing address of the cardholder.
phone
References: Capture Info.Phone
XML Representation: attribute
Attributes:
Default Value
Phone number associated with mailing address of the cardholder.
email
References: Capture Info.Email
XML Representation: attribute
Attributes:
Default Value
Email address associated with the cardholder.
gatewayTransactionId
References: Capture Info.Reference Number
XML Representation: attribute
Attributes:
Default Value
Transaction identification in gateway.
approvalCode
References: Capture Info.Approval Code
XML Representation: attribute
Attributes:
Default Value
Authorization code returned by Provider that approved this transaction. In some instances might also be used to store response code returned by Provider when transaction declines.
responseDate
References: Capture Info.Response Date
XML Representation: attribute
Attributes:
Default Value
Date of the response.

In API response, the date is returned in yyyy-MM-dd HH:mm:ss format.
responseCode
References: Capture Info.Response Code
XML Representation: attribute
Attributes:
Default Value
Gateway generated response code.
responseMessage
References: Capture Info.Response Message
XML Representation: attribute
Attributes:
Default Value
address
References: Capture Info.Address
XML Representation: attribute
Attributes: Calculated
Default Value

XML Sample:

<processing-info
    id="" 
    createDate="" 
    holderName="" 
    accountNumber="" 
    accountAccessory="" 
    token="" 
    street="" 
    city="" 
    state="" 
    zipCode="" 
    phone="" 
    email="" 
    gatewayTransactionId="" 
    approvalCode="" 
    responseDate="" 
    responseCode="" 
    responseMessage="" 
    address="" />

"<processing-info id=\"\" createDate=\"\" holderName=\"\" accountNumber=\"\" accountAccessory=\"\" token=\"\" street=\"\" city=\"\" state=\"\" zipCode=\"\" phone=\"\" email=\"\" gatewayTransactionId=\"\" approvalCode=\"\" responseDate=\"\" responseCode=\"\" responseMessage=\"\" address=\"\" />"

JSON Sample:

{
  "id": "",
  "createDate": "",
  "holderName": "",
  "accountNumber": "",
  "accountAccessory": "",
  "token": "",
  "street": "",
  "city": "",
  "state": "",
  "zipCode": "",
  "phone": "",
  "email": "",
  "gatewayTransactionId": "",
  "approvalCode": "",
  "responseDate": "",
  "responseCode": "",
  "responseMessage": "",
  "address": ""
}

Query String Sample:

?id=&createDate=&holderName=&accountNumber=&accountAccessory=&token=&street=&city=&state=&zipCode=&phone=&email=&gatewayTransactionId=&approvalCode=&responseDate=&responseCode=&responseMessage=&address=&
id=
createDate=
holderName=
accountNumber=
accountAccessory=
token=
street=
city=
state=
zipCode=
phone=
email=
gatewayTransactionId=
approvalCode=
responseDate=
responseCode=
responseMessage=
address=