" Web Developer's Toolkit "

The QuickCommerce Web Developer's Toolkit is intended to be used by advanced application/web developers. Limited support is available for questions beyond the scope of this document.

AuthRequest.asp

For all transaction types Returns additional information for developers (such as AVS data, Authorization Code, and whether the request was Accepted or Declined) For a more seamless and customized look, control of the browser is never given to QuickCommerce (our system will not display any Web page whatsoever) Generates and returns a comma-delimited string, not to be displayed within a browser.  Therefore developers should generate or "imitate" the http request using any number of available techniques for the desired scripting environment.  The returned string may then be parsed to retrieve the desired data. Developer is responsible for collecting credit card information which should then be sent to AuthRequest.asp (along with all other data) using SSL encryption. Allows the ability to reject an AVS (Address Verification Service) mismatch. Supports additional features such as ECHODATA and TESTREQUEST.

AuthPost2.asp

For all transaction types Returns additional information for developers (such as AVS data, Authorization Code, and whether the request was Accepted or Declined) Accepts and returns standard browser form POST or GET methods. For a more seamless and customized look, the developer is allowed to disable the QuickCommerce receipt page (our system will not display any Web page whatsoever) In all cases, either a displayable html page is generated (a receipt or declined message), or a Script/URL of the merchant's choosing is immediately called using query line variables to return data. If desired, a Silent Post can be generated immediately upon the transaction, regardless of what else happens. Either the developer can be responsible for collecting credit card information which should then be sent to AuthPost.asp (along with all other data) using SSL encryption, or the developer can use AuthPostWebLink.asp to allow QuickCommerce to collect this information. Allows the ability to reject an AVS (Address Verification) mismatch. Supports additional features such as ECHODATA and TESTREQUEST.

AuthPostWebLink.asp

Collects credit card and other information before posting it to AuthPost.asp Accepts and forwards all variables accepted by AuthPost.asp

VendorUpdateMerchant.asp

Updates a merchant's configuration

CaptureRequest.asp

Capture a previous AuthOnly

VoidRequest.asp

Void a previous current transaction

* Additional scripts are being developed to support automated transaction Settlement requests, Batch uploading and downloading, and Reporting functions.

IMPORTANT POINTS ABOUT THE TOOLKIT

The following relevant QuickCommerce features cannot be controlled or changed directly with this Toolkit.  They all, however, can be edited or changed by the QuickCommerce account holder via their merchant account login/menu:

The merchant's password cannot be changed or requested.

If the merchant has requested an e-mail for each transaction through their merchant configuration on QuickCommerce, this cannot be overridden with the Toolkit.

If the merchant has specified that unique invoice numbers should be enforced, they are NOT enforced within the Toolkit scripts.  It is considered the web developer's responsibility to ensure that duplicate requests are not made.

If the merchant does not accept an ACH, it will be enforced within the Toolkit as well. (with the exception of a TESTREQUEST)

If the merchant has placed their account into test mode, this CANNOT be overridden directly within authrequest.asp.  The merchant must be in live mode and the TESTREQUEST variable must be left out (or not "TRUE") for a transaction to be considered live.

This work is © Copyright 1999 by E-Commerce Exchange. All trade marks and brand names are acknowledged as belonging to their respective owners.