GoGreen PC Tune-Up™
Learn More

Insta-Install™
this is how ssl encrypt our websites
MTNCOMP | List View | Table View | myBlog (1755 Entries)
myBlog Home

Blog


JavaScript XML ASP Classic e-commerce integration programming with Authorize.Net - Part 1

by Mountain Computers Inc, Publication Date: Saturday, February 10, 2024

View Count: 264, Keywords: Authorize.Net, ASP Classic, JavaScript, XML, Hashtags: #Authorize.Net #ASPClassic #JavaScript #XML



Earlier this week I started on a new project to revitalize an existing e-commerce site that I last touched and integrated back in 2014. Been running good for 10 years yet Bank of America had to change their partnerships.
 
I will share some notes on how the integration gets started here in Part 1 and part 2 with what I learned and the results.
 
Here are my notes:
 
* existing integration - keep that running and make sure you don't contaminate it
* new integration - run that in parallel on the live system
* determine client or server side user input for credit card and payment input
* write code for both client and server side data I/O just in case you need options
* upgrade security on the new integration where possible and test failure
* do unit testing as you go, and limit your units to very small packages
* reach out to solution providers for examples; stackoverflow, developer cybersource, etc.
* enable secure debugging and ensure you are on an SSL connection
* backup your documentation and working code as you go, version control 101
* error handling, use logical and secure messages and methods to ensure easy debugging
* when ready to go live, get stakeholder approval
* continue monitoring
 
Languages involved:
* Classic ASP
* JavaScript
* HTML/CSS
* SQL-MS-Access/OLE-DB databases
* XML/JSON messaging
* Secure Tokens
 
ETA 5-10 business days. 5 at best, 10 at worst.
 
When getting started, remember the following:
1. Remember to get your Authorize.Net LIVE account as Administrator, not Owner under your own email account so you don't have to bother the Owner with PIN verification requests.
2. Remember to get your free Authorize.Net SANDBOX account as Corporate for the most features you will need.
3. Remember to create a new Authorize.Net LIVE account as Owner for the email where e-commerce transactions are to be processed since the original OWNER email address when the Authorize.Net Account was created could be the owner's work email address instead of the actual email address for receiving Authorize.Net notifications, reports, transactions and settlements. Just turn off the notifications under the Original OWNER account and turn on all notifications for the actual transaction processing OWNER account.
 
REF 1: https://developer.authorize.net/api/reference/features/accept_hosted.html
REF 2: https://developer.authorize.net/api/reference/index.html
REF 3: https://sandbox.authorize.net/
REF 4: https://developer.authorize.net/api/reference/index.html#gettingstarted-section-section-header
REF 5: https://developer.authorize.net/api/reference/index.html#accept-suite-get-an-accept-payment-page
 
Annoying part of documentation is the following is hidden on the getting started page. its collapsed when it should be in plain site for First Time User. Here is the info that you need to digest first before doing anything else.
 
FIRST TIME USER? Click here for API Endpoints & Authentication details
API Endpoints & Authentication
All requests to the Authorize.net API are sent via the HTTP POST method to one of our API endpoint URLs.
HTTP Request Method: POST
Sandbox API Endpoint: https://apitest.authorize.net/xml/v1/request.api
Production API Endpoint: https://api.authorize.net/xml/v1/request.api
XML Content-Type: text/xml
JSON Content-Type: application/json
API Schema (XSD): https://api.authorize.net/xml/v1/schema/AnetApiSchema.xsd
All calls to the Authorize.net API require merchant authentication. Sign up for a sandbox account to quickly get started. 
 
A Note Regarding JSON Support
The Authorize.net API, which is not based on REST, offers JSON support through a translation of JSON elements to XML elements. While JSON does not typically require a set order to the elements in an object, XML requires strict ordering. Developers using the Authorize.net API should force the ordering of elements to match this API Reference.

Alternately, consider using the Authorize.net SDKs for a seamless integration. 
 
continue to Part 2 of this post
 
more to come...

if you found this article helpful, consider contributing $10, 20 an Andrew Jackson or so..to the author. more authors coming soon
FYI we use paypal or patreon, patreon has 3x the transaction fees, so we don't, not yet.

© 2024 myBlog™ v1.1 All rights reserved. We count views as reads, so let's not over think it.