The API contains these subroutines, files, and templates:
|
Subroutine, File or Template |
Description |
|
w3CCheck |
Validates a credit card number and return the credit card type. |
|
w3HTMLeComBeg |
Beginning of the Transaction form. |
|
w3HTMLeComEnd |
End of the Transaction form. |
|
w3HTMLeComCCInfo |
Inserts the credit card information in the Transaction form. |
|
w3HTMLeComCKInfo |
Inserts Electronic Check information in the Transaction Form. |
|
w3HTMLeComEMailInfo |
Inserts e-mail information in the Transaction form. |
|
w3HTMLeComRecurring |
Inserts recurring information in the Transaction form. |
|
w3CClnclude |
This file contains the definition of all the user arrays. These arrays are parameters to the API subroutines. Add this include in all your applications that use the user arrays. |
|
MT.Template |
Default template for the Transaction form. |
|
CC.Validation |
Template that contains the JavaScript code to validate credit card numbers before the Transaction form is submitted to the Internet bank. This template is used by the w3HTMLeComCCInfo application if the CCCheck flag is set to 1 in the CCInfo file. |
To use the API:
Call w3HTMLeComBeg to start the Transaction form.
Gather the checking or credit card information (depending on the payment type) from the client and call w3HTMLeComCCInfo for credit card authorization (or call w3HTMLeComCKInfo for electronic check authorization).
To send an e-mail message to the user when the transaction is validated, run w3HTMLeComEMailInfo.
To bill the user on a recurring basis (for example, for a subscription), run w3HTMLeComRecurring.
Insert a submit button in your template to submit the Transaction form. The default template (MT.Template) has an example of the submit button in the MT.Submit section.
Call w3HTMLeComEnd to close the Transaction form.
|
NOTE |
Sample applications are located in the www account’s bp file. The applications names are cc.Driver, mt.selectpayment, MTAccept, and MTDecline. |