DOTS BIN Validation is a web service that provides information about charge cards. By using the first six digits of the card number (aka BIN or Bank Identification Number), DOTS BIN Validation provides information about the charge card itself as well as the bank that issued the card.
With BIN validation, users can verify bank and charge card information to protect against fraud and superfluous charge-backs. This information can be used to improve online applications or as supplemental information for existing databases.
Developer Guide Map
This section lists the DOTS BIN Validation operations and goes into the details behind the inputs and outputs.
ValidateBIN_V2 (Recommended Operation)
This section reflects details on the error outputs that can happen with the service.
Here you'll find code snippets for various programming languages and frameworks along with links to our sample code page on the web site.
This is where you'll go to take the API for a spin. There you can test our recommended operation ValidateBIN_V2.
In this section you'll find all the different endpoints supported by this service, input and output schema information as well as an opportunity to try the other endpoints as well.
This is a list of some of the questions we hear more often that you can reference and get answers on right away.
Integration of DOTS BIN Validation into user applications is generally a straightforward process. For common programming platforms, such as ASP, ASP.NET, ColdFusion, PHP, etc., Service Objects will likely have sample code available online:
BV - Code Snippets and Sample Code
If the code you seek is not available online, you can ask Service Objects to build a custom example for you. Email firstname.lastname@example.org for more details.
Web Service Structure
Web services provide a standard interface to encapsulate tricky business logic. They allow simple integration of applications via the web. Service Objects has followed web services best practices and come up with some of its own standards to ensure that its web services are as easy to integrate, and as accessible as possible.
The host path, or physical location of the web service is here:
The location of the WSDL, or Web Service Definition Language document, is here (This is also accessible via the "Service Definition" link.):
Service XML Request Help Page
Service JSON Request Help Page
SOAP is done via POST, only with special XML markup in the post-body.
The WSDL is an XML document that defines the interaction web service, meaning its inputs, outputs, operations, and the like. Most likely, you will have another tool read this WSDL and make the operations available to you in your application via some type of proxy class. Whenever your utilities or IDE asks for a WSDL path, you can provide this one.