SecureCreditServer - How It Works

SecureCreditServer - Simple, Secure, Real-Time

Enabling credit-aware e-business solutions through existing Internet infrastructure

After subscribing to SecureCreditServer, the credit request is made using standard credit bureau inputs. These inputs are formatted according to a published XML schema, and correspond to current input requirements. This process makes it easy to use an existing relationship with a credit data provider, or utilize the reselling services of SecureCreditServer.

This represents significant gains for the developer because credit bureaus are not accessible through common communication systems and use varying data formats. SecureCreditServer provides a common interface to credit data and analysis providers.

As new capabilities and services emerge, SecureCreditServer will expose the new features through OmniDrive™ technology. The OmniDrive system shields the SecureCreditServer developer from the necessity of staying up-to-date with new products and input requirements of the credit bureaus. Your request for data is mapped to the most current input standards available, in a completely transparent process.

SecureCreditServer dramatically lowers the cost of entry for e-business solutions by bridging the gap between data providers and the Internet communications industry. Leverage your existing web development resources and infrastructure with SecureCreditServer.

Special Notice to Application Service Providers
We understand your business. SecureCreditServer was built to cater to your specific needs and to ensure your success. We offer special pricing and assistance. Contact Us for more details.

Process Workflow

Step 1: Request Data
The request is made from an Internet accessible server ("Client"), through an encrypted channel. This programmatic request conforms to the SOAP consumer standard and contains a valid request XML document.

Step 2: Request Confirmation
Confirmation of the request is received in the form of a session key that will be used for retrieving the credit stream. It is the responsibility of the developer to maintain this key and prevent multiple requests.

Step 3: Retrieving Results
The session key acquired in step 2 is used to retrieve the credit stream. The result is an XML Response document that conforms to the published standards.

Step 4: Calculating Results
Because the data returned is in XML format, the scoring calculations are completely extensible. You can use any combination of bureau provided scoring mechanisms, or customize your own based on the available data.