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.


SubscriptionAdjustment

Type:  
Abstract:  no
Status:  Active
Adjustment applied to a subscription transaction.
Available Fields:
id
References: Adjustment.Id
XML Representation: attribute
Attributes:
Default Value
Identifier of the object used for references; auto-incremented integer value.
effectiveDate
Type: Datetime
XML Representation: attribute
Attributes:
Default Value
The date must be submitted in yyyy-MM-dd format.
endDate
Type: Datetime
XML Representation: attribute
Attributes:
Default Value
The date must be submitted in yyyy-MM-dd format.
note
References: Adjustment.Notes
XML Representation: attribute
Attributes:
Default Value
Any additional information about the adjustment.
type
References: Adjustment.Adjustment CL
XML Representation: attribute
Attributes:
Default Value
Represents the type of selected funds adjustment.
length
References: Adjustment.Length
XML Representation: attribute
Attributes:
Default Value

XML Sample:

<subscription-adjustment id=""  effectiveDate=""  endDate=""  note=""  type=""  length="" />

"<subscription-adjustment id=\"\" effectiveDate=\"\" endDate=\"\" note=\"\" type=\"\" length=\"\" />"

JSON Sample:

{
  "id": "",
  "effectiveDate": "",
  "endDate": "",
  "note": "",
  "type": "",
  "length": ""
}

Query String Sample:

?id=&effectiveDate=&endDate=&note=&type=&length=&
id=
effectiveDate=
endDate=
note=
type=
length=