The XML gateway API is a programming interface that resides on transaction servers which communicate directly to credit card processing networks. The programming interface requires that the freelancer be sufficiently knowledgeable in programming skills in any programming or object oriented scripting language.
The XML Gateway API accepts the card purchasers information, including credit card information, billing address, total charge amount and order id and produces an authorization or decline directly from the merchant bank.
The information is passed via 128bit SSL https post in XML format. That post occurs in the background from our server. Thus the purchaser never leaves our website. The authorization information is returned in XML format with full error trapping and reporting to indicate the success or failure of the transaction.
we will provide the much deeper guidelines and documentation. this project involves developing the already developed Joomla template!
you can access the template at: [url removed, login to view]
backend panel: [url removed, login to view]
1. The our website produces the XML with all the required information depending on the operation type and performs an https (silent POST) to the gateway transaction servers.
2. The gateway’s transaction servers determine the operation type and execute it.
3. Once the correct operation is carried out, the gateway assembles the response in XML.
4. The gateway’s transactions servers send the XML response to the merchant’s web or transaction
servers indicating a success, failure or error.
5. Our server parses the XML and notifies the customer or user of a successful request, failure or
Requirements for XMLGateway Utilization
1. Processing Platforms Supported.
a. FDR (Omaha Platform)
b. Elavon (Formerly Nova)
c. Paymentech (Tampa Host Capture Platform)
d. TSYS (formerly Vital/VisaNet)
e. ACH (FirstFund)
2. Transaction Center ID
a. Numeric access key assigned by our credit card processor
b. Unique to merchant
c. Cannot be changed
d. Required for API integration
3. Gateway ID
a. Alpha&#8208;numeric passphrase assigned by our credit card processor
b. Can be changed via the gateway options area in the Transaction Center
c. Should be changed every 90 days to ensure security
d. Required for API integration
e. Retrieved from the options tab in the Transaction Center (our credit card processor)
4. MID / TID /Processor
a. These parameters are only used for accounts that have multiple merchant accounts associated with a single transaction center id.
b. If your account has multiple ACH accounts and you want to specify which one to process a transaction under, simply submit the mid parameter with the 3 character ACH username we have been assigned for that account.
c. The values needed for each account can be found within our Transaction Center.
5. Secure URL
a. Test account is available
b. Full test account information is documented
WILL PROVIDE WITH THE SAMPLE CODES and FURTHER DOCUMENTATION
2 freelancers are bidding on average $175 for this job
I have done this type of similar project before.I have been working for a project like [url removed, login to view],I'm very experienced in this type of [url removed, login to view] I have 6 members in my team [url removed, login to view] propose to furnish labor and materials fo More