Chargeback File
Global Chargeback Registry

Visa, MasterCard, American Express, Discover and Paypal Chargeback Registry

User login

API Integration

In order to utilize the Chargeback File API, you must have a valid and current API Security Key which can be obtained freely by signing up now.

Request URL

https://api.chargebackfile.net/search

GET versus POST
Chargeback File may be accessed by either GET or POST methods; however it is recommended that you utilize POST commands to

https versus http ?
There are a variety of reasons including privacy, security and data integrity that would suggest that you should utilize https for contacting to Chargeback File; however that is not a requirement.

Input Parameters

Required
api_key=

Secondary (Must Provided At Least One)
card_number=
email_address=
username=
ip_address=
telephone_number=
content=

Optional
id=

Response Fields

transaction varchar(15)
error char(1)
file char(1)
response varchar(250)

Examples

Example Request
https://api.chargebackfile.net/search?api_key=test&ip_address=127.0.0.1&...

Example Response
transaction=qcx7YoqCob26Oa3;error=0;file=0;response=Invalid IP Address,;

Transaction Errors

Whenever an error occurs, an error=1 will be generated causing one of the following response codes to be generated.

Invalid API Key

Invalid Request Type

Maximum Search Requests Exceeded

No Search Field Submitted

Invalid Card Number
Invalid Email Address
Invalid Username
Invalid IP Address
Invalid Telephone Number
Invalid Content

Possible Response Codes

Whenever a chargeback is on file for a submitted transaction, a file=1 is generated with one or of the following response codes.

Chargeback File on Card Number
Chargeback File on Email Address
Chargeback File on Username
Chargeback File on IP Address
Chargeback File on Telephone Number
Chargeback File on Content

Submitting Card Numbers

It is highly recommended that you provide an MD5 Hash card number, however the system will accept plain text card numbers. When a plain text card number is provided, you are required to utilize https and POST methods, all other request will generate an error and "Invalid Request Type" response.