Recurring billing API
The 360 One Recurring Billing Solution (RBS) is designed to assist clients who process installment or recurring billing, and desire a system to manage and automate processing transactions on a regular basis.
Contents
The API interface is a simple POST message, therefore language is up to the developer.
Introduction
Using the 360 One RBS, clients may create, edit, and delete customer billing records. These records contain the information needed to process transactions and meet all credit card interchange requirements.
System Features
- Dynamic Descriptors
- ACH support
- Web interface in addition to the API
- Simple POST interface
The client begins by creating a customer record using the RBS API, part of the 360 One web services. This record is stored in the 360 One secure Oracle database. A daily timed event submits records scheduled to be processed that day to the 360 One Payment Gateway. The gateway processes the requests and receives the response from the credit card networks. All transactions whether approved or declined are added to the database, and are accessible through the 360 One web reporting system.
Technical Overview
In order to begin utilizing RBS, a certification process must be completed between the client and 360 One. A member of the 360 One certification team will be assigned to work directly with each client. The primary goal of certification is to validate that the RBS API request is formed accurately and transmitted successfully. Merchants must be certified to the 360 One Payment Gateway and have a live web login before completing certification to RBS.
There are three request types available to RBS: Create record, Update record, and Delete record. Each are detailed below:
Example Create request
- POST /srv/api/rbsCreate HTTP/1.1
Content–Type: application/x–www–form–urlencoded
Cache–Control: no–cache
Pragma: no–cache
User–Agent: Java/1.7.0_21
Host: test.merchante–solutions.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 578
userId=pjomes&userPass=xxxxx&profileId=94100001234500000001&customer_id=ABC1234&card_number=1234567890&card_exp_date=0614&recur_amount=25.00&recur_start_date=6/15/14&frequency=MONTHLY&recur_num_pmt=12
Example Create response
The result will contain a simple three digit error code, where 000 means no error occured, in addition to a plain-text response message.
- rspCode=000&rspMessage=OK
Example Update request
- POST /srv/api/rbsUpdate HTTP/1.1
Content–Type: application/x–www–form–urlencoded
Cache–Control: no–cache
Pragma: no–cache
User–Agent: Java/1.7.0_21
Host: test.merchante–solutions.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 578
userId=pjones&userPass=xxxxx&profileId=94100001234500000001&customer_id=ABC1234&card_number=2345678901&card_exp_date=0616
Example Update response
- rspCode=000&rspMessage=OK
Example Delete request
- POST /srv/api/rbsDelete HTTP/1.1
Content–Type: application/x–www–form–urlencoded
Cache–Control: no–cache
Pragma: no–cache
User–Agent: Java/1.7.0_21
Host: test.merchante–solutions.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 578
userId=pjones&userPass=xxxxx&profileId=94100001234500000001&customer_id=ABC1234
Example Delete response
- rspCode=000&rspMessage=OK
For all available fields, please see the Recurring Billing specification.
