 |
|
|
 |
|
 |
|
|
|
|
 |
|
|
|
|
 |
|
|
|
|
 |
|
|
|
|
 |
|
|
|
|
 |
Free Bi-Monthly
Marketing Newsletter
|
|
|
|
|
|
 |
Merchants, Click
Below To Login
|
|
|
|
|
|
|
|
The following script represents the latest QuickCommerce interface for developers desiring to submit an "Authorization Request" via http and receive a response in easy-to-use form variables that indicates:
- Whether the request was accepted, declined, or invalid
- Why the request was declined or invalid
- AVS result
- Authorization Code
- QuickCommerce Transaction ID
AuthRequest.asp is designed for developers who wish to use form variables in their request, and receive form variables in the response. Just as in our traditional script WLDoTrans.asp, AuthPost2.asp relies on the merchant's QuickCommerce configuration in order to function properly. This configuration can be edited by the merchant after using the Merchant Login. Here he will specify the "Return script or link URL" which will determine where AuthPost2.asp will take the buyer after the transaction has been processed (begin this value with http://). Here he must also make sure the "Return URL Method" is set to POST if AuthPost2.asp is to return any data whatsoever. If the merchants specifies a "Silent POST script URL", then AuthRequest.asp will send a second response to this URL outside of the browser interface (this is especially useful for the developer who needs to be informed of a successful purchase, even when the buyer neglects to click the Continue button on his QuickCommerce receipt. It becomes less useful when this receipt is disabled) For those developers who wish to act in behalf of the merchant and set these configuration values in an automated fashion, the script VendorUpdateMerchant.asp can be used to update a merchant's configuration (recommended for generic software packages such as shopping carts).
|
|
HTTP REQUEST FIELDS
LOGIN
Required for transactions other than test transactions. This is the assigned QuickCommerce login id.
PASSWORD
Required for Credit or Post Authorization transactions. For details on the use of transaction types, see the QuickCommerce User's Guide.
INVOICE
The order/transaction invoice number. It may be required to be unique according to the merchant's configuration. Uniqueness is determined by matching invoice numbers with the current day's existing invoice numbers only)
DESCRIPTION
Order/Transaction Description (This field will be trimmed to the first 80 characters before being stored by QuickCommerce)
AMOUNT
Order/Transaction Amount that authorization is requested for. The amount may only be negative for Credit transactions. A decimal point and 2 digits are required.
CUSTID
Your own assigned customer id the transaction.
METHOD
May be one of: VISA, MASTERCARD, AMEX, DISCOVER, JCB, ACH
TYPE
May be one of:
NA (means Normal Authorization)
AO (means Authorization Only)
CR (means Credit)
PA (means Post Authorization)
CARDNUM
Any valid Credit Card Number (not submitted or left blank for ACH transactions)
EXPDATE
Any valid Credit Card Expiration Date (not submitted or left blank for ACH transactions)
AUTHCODE
Required for PA transaction types. (not submitted or left blank for all other transaction types)
ACCTNO
Checking Account number (numbers only - no spaces or characters. not submitted or left blank for all credit card transactions)
ABACODE
Bank 9 digit ABA Transit and Routing Code (numbers only - no spaces or characters. not submitted or left blank for all credit card transactions)
BANKNAME
Name of bank where checking account exists. (Can be left blank. not submitted or left blank for all credit card transactions)
NAME
Buyer's name (Cardholder's name for credit card transactions, or Accountholder's name for ACH transactions)
ADDRESS
Buyer's address (used for Address Verification Service validation on credit card transactions)
CITY
Buyer's city
STATE
Buyer's state
ZIP
Buyer's ZIP (used for Address Verification Service validation on credit card transactions)
COUNTRY
Buyer's country
PHONE
Buyer's Phone
FAX
Buyer's Fax
EMAIL
Buyer's E-mail
USER1 - USER10
Relevant only to your own programming. These fields are not stored in the merchant's QuickCommerce batch records.
REJECTAVSMISMATCH
If this field is not provided with a value of "TRUE", the transaction will be accepted if it is authorized by FDC, even if the AVS response is a mismatch. Otherwise, the transaction must pass the "AVS test" with either a matching zip code, address, or both.
TESTREQUEST
If this field is provided with a value of "TRUE" the script will perform all validation functions except actually authorizing the transaction and storing it in the merchant's batch, regardless of whether the merchant's configuration is set to LIVE or TEST mode. In other words, the response would be equivalent to the merchant being in TEST mode
DISABLERECEIPT
Provide this request field set to "TRUE" if you wish to suppress the QuickCommerce receipt and receive the response variables directly to the script specified in the "Return script or link URL" value within the merchant's configuration (see the explanation at top of page). If you disable the receipt in this manner, it will not effect the type of response data that will be returned by AuthPost2.asp If you do not use DISABLERECEIPT, AuthPost2.asp will print a receipt containing a button or link which will return the buyer to the "Return script or link URL" value specified within the merchant's configuration. Regardless of whether this feature is used, AuthPost2.asp will display an error message if data which is obviously invalid is received (Example: The expiration date is missing). These error messages are designed to aid the buyer in entering complete and correct information, however if the developer wishes to display his own error messages, he would simply do his own validation checking before posting to AuthRequest.asp .
|
|
|
HTTP RESPONSE FIELDS
RESPONSECODE
May be one of the following: A - Accepted/Authorized
P - Pending (treated as Accepted/Authorized; applies to ACH or Post Auth transactions)
D - Declined
R - Referral/Call Voice Center (treat as decline)
E - Error
T - TEST MODE
AUTHCODE
This field will contain the authorization code returned from FDC. Or in the case of a PA transaction type (Post Auth), it will contain the authorization code provided in the REQUEST field AUTHCODE.
DECLINEREASON
This field will be blank for an accepted or TEST transaction response code (A,P or T); otherwise it will contain the reason for the response code.
AVSDATA
This field will contain a 3 character string if an AVS response is available for the transaction. Each character represents a match/mismatch. The first character is the Address match code, the 2nd character is the Zip code match code, and the 3rd character is a combined code. Possible AVS codes are: A, Y, N, Z, X . A match response would be a "Y". In the event that the REQUEST field REJECTAVSMISMATCH is set to TRUE, at least one of the 3 characters of the AVS response must be a Y for the transaction to be accepted.
TRANSID
This field is the internal QuickCommerce ID for the transaction. It is to be used for voiding and capturing transactions using QuickCommerce (when those features are available). A "capture" is only necessary for an AO transaction type.
All remaining RESPONSE fields are echoed from the original REQUEST fields, in this order:
( when ECHODATA = "TRUE" )
LOGIN
INVOICE
AMOUNT
METHOD
TYPE
DESCRIPTION
CUSTID
NAME
ADDRESS
CITY
STATE
ZIP
COUNTRY
PHONE
FAX
EMAIL
USER1
USER2
USER3
USER4
USER5
USER6
USER7
USER8
USER9
USER10
|
|
|
|
