Navigation:  Reference > Functions >

X_Charge()

Print this Topic Previous pageReturn to chapter overviewNext page

X_CHARGE(1,2,3,4,5,6,7,8)

PURPOSE

This function is to Interface the X-charge Credit Card system. To use this function will require a third party program & services provided by X-Charge credit card processing software Copyright 2005 CAM Commerce Solutions, Inc.

If you want to implement Credit card processing in your Tas Professional program please contact Computer Accounting Solutions and we will get you and your customers setup using this function.  Also when your customers sign up to use X change they will provided hardware to capture credit card information for this process. Call 928-257-1236. Credit Card processing services from X Change are limited to only the United States. This is an easy way to provide credit card processing for your applications.

PARTS

1. sac Required - What to do:

xSetup - Setup Routine for the X-Charge system

xSubmitCC – Submit Credit card

xSubmitDebit - Submit Debit Card

xResponce - Check for Response

xVoidCC - Voids Credit Card Transaction.

xCreditReturn - Credit Return

xVoidReturn - Void of Return

xForceSale - Force Sale

xPreAuth - Pre Authorize of Sale

xDebitReturn - Debit Return

xGuarDL - Check Guarantee with Driver license

xGuarMirc - Check Guarantee with Mirc Code

xReport - Processing Report.

pPInitalize - Initialize the Pin Pad Device (no Parameters)

pPConfig - Configure the Pin Pad Device (no Parameters) Note: Put up Configuration Dialog box

pPPrompt - Prompt the Pin Pad Device

pPClose - Close the Pin Pad Device (no Parameters)

pPDisplaytext - Display Text on Pin Pad Device

pPDisplayLogo - Display Logo on Pin pad Device (if compatible)

pPPromptSignature - Prompt Signature on Pin Pad Device

2. f/c/e

xSetup – Optional - Folder for x-charge transaction folder Note: this can also be stored in the taspro.ini file.

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - Account code (in Alpha)

xReponce - Optional – XNoWait - If Used the Response will not wait for a response but only check and return (otherwise the system will wait for a response from The X-charge system)

xGuarDL,

xGuarMirc – Amount (as Alpha)

xReport - Report type : CCTOTAL,TRANTOTALS, or TRANDETAILS

ppPrompt – Debit Card number (alpha)

ppDisplaytest – Text to Displayed

ppPromptSignature – Text to Display with Signature request.

3. f/c/e .

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - Expiration Date(in Alpha)

Note: In as Scanned transition add the Scan data.

xGuarDL,

xGuarMicr - Customer name

xReport - Start date for report (MM/DD/YY)

ppPrompt – Amount of transaction (alpha)

4. f/c/e

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - Amount to charge (in Alpha)

xGuarDL - Drivers license Number

xGuarMicr - ABA #

xReport - End Date for report (MM/DD/YY)

5. f/c/e

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - Invoice/reference number (in Alpha)

xGuarDL,

xGuarMicr -Optional - Clerk (alpha 20)

xReport - Clerk (Alpha 20)

6. f/c/e

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - CCV Code(in Alpha)

Note : CCV Code is only if not scanned.

xGuarDL - State – 2 character Abbreviation

xGuarMicr - Account Number

xReport - Group by – options : CCENTRY, CLERK, or REGISTER

7. f/c/e

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - As the Address (in Alpha)

Note: Address is only required is not scanned

xGuarDL - Date of Birth (an Alpha in the format of MM/DD/YY)

xGuarMicr - Check number (alpha 6)

xReport - String container class (Note: This needs to be a TASString or memo )

8. f/c/e

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - Zip Code (in Alpha)

Note: Zip Code is only required is not scanned

xGuarDL - Check Number (Alpha)

xReport - String Container Class Object (Lines or stings)

RETURN TYPE – Varies

xSubmitCC,

xSubmitDebit,

xCreditReturn,

xDebitReturn,

xVoidReturn,

xForceSale, - Logical – False if Processing file can not be created.

xReponce – Authentication String (or Error Code)

xGuarDL,

xGuarMicr - Logical - False if Processing file can not be created (use xReponce for Auth code)

ppInitalize - Logical – False if Can’t initialize the the pin pad Device.

ppConfig - Alpha – Description of Error.

ppPrompt - Alpha - Pin key and Pin Block Separated with ‘[‘ and ‘]’

ppClose – Alpha – Description of Error.

ppDisplayText – Alpha – Description of Error.

ppDisplayLogo – Alpha – Description of Error.

ppPromptSignature – Alpha – Bit map of the Signature (Not Tested)

COMMENTS

NOTE: The special alpha constants above (Xnowait, xSetup, xSubmitCC, xResponce, xSubmitDebit, XVoidCC, XCreditReturn, XVoidReturn, XForceSale, XPreAuth, XDebitReturn, XGuarDL, ,XGuarMirc, XReport, PPInitalize, PPConfig, PPPrompt, PPClose, PPDisplaytext, PPDisplayLogo, and PPPromptSignature,) are defined in COMPILERCONSTANTS.TXT.

NOTE: If you use this feature and integrate your software to use X-Charge for your customers. Computer Accounting solutions will split the X-Change commissions with you 50/50 and give you support for free and an unlimited runtime LIC for TAS Professional 7 making this a win win for both developers. Just think real residual income.  Making this a win win for both CAS and you the developer. See: www.cassoftwarex.com for more details.

EXAMPLE

See CreditCard.src and CreditCard.DFM

 


Page url: http://www.cassoftware.com/tas/manual/x_charge.htm