VP-ASP :: Shopping Cart Software

Shopping Cart Software Solutions for anywhere in the World

US/Canada(Toll Free): +1 888 587 2278
Europe/UK: +44 (020) 7193 9408
Australia/New Zealand: +61 3 9016 4497

Gateways

Bank or Electronic Payment Systems

        

Adding your own payment system

The electronic payment system normally consists of two new files. One file interfaces to the gateway.

The second file handles the status return back from the electronic gateway. There are no other changes to VP-ASP code.

In addition to the two files mentioned above, the configuration file shop$config.asp is updated to point to the replacement shopcheckout.asp        

Examples of Electronic Payment System

If you requested the electronic payment add-on for Verisign, we would send you two to four new files: In this example, Verisign has three files. A read me file comes with these files. Follow the simple instructions.

Verisignshopcheckout.asp

VerisignResult.asp

Versigngateway.asp

You will also need to update your merchant identifier supplied by the electronic gateway system. This is done by editing verisigngateway.asp         

Multiple Payment Methods

Multiple different payment methods can be used at the same time. If you are using a gateway you may wish to turn off the standard VP-ASP credit card and non credit card payment forms. This is done by setting the following in Shop configuration.

Xallowcreditcards

No turns off standard VP-ASP card form

Xallowotherpayments

No turns off other payment types

        

Turning Off VP-ASP Credit Card Collection

All the gateway interfaces allow you to also collect credit card details in case your gateway stops functioning temporarily. You can turn this facility off by setting:

xallowcreditcards

No turns off VP-ASP credit card form on the same page as the gateway form

xallowotherpayments

No, turns off other payment options

        

Bank or Electronic Payments Systems

VP-ASP supplies add-ons for electronic payment systems. In addition our general interface allows you to configure a new payment system in about 1-2 hours. These are free on request add-ons to VP-ASP customers but they do not undergo the same testing procedures and may be supplied on an as-is basis. There are limits to the number og gateways supplied per license. Normally this is three.

VP-ASP does not require an electronic gateway. By default it stores payment details in the database and allows you to view those payment using the display orders facility.

VP-ASP supports over 70 gateways. Please visit www.vpasp.com/virtprog/vpasp_epsystems.htm

Gateway

2Checkout

Anz Egate

Australia Post

AuthnetSSL

Authorizenet

Bank of America

Bluepay

Echonline

Clikpay

Directone

DPI

Ematters

Egateway

Eprocessing

ESEC

Eway

EZPN

Firstpay

Goemerchant

Goemerchant API

InternetSecure

Innovative

Iongate

ICP

Intellipay

InternetSecure

Itransact

Linkpoint

Merchant Trust

Mirapay

Moneris

NAB

NoChex

Paybycheck

Paygateway

PaymentTech

Payments International

Paypal

Payready

PlugnPay

Protx

Psigate

QuickCommerce

SecurePay

SecureTrading

Skipjack

Technocash

TPPRO

Verisign Payflow Link

Verisign Payflow Pro

USAEPAY

Viaklix

Worldpay

And many others         

Paypal

VP-ASP supports both normal Paypal and Paypal IPN (Instant Payment Notification). Paypal is a common method to pay for goods and services over the Internet. VP-ASP also supports Paypal multi currencies.

The basic PayPal gateway is included with all versions of VP-ASP. For PayPal IPN you will need to purchase one of our Power Pacs.

VP-ASP also supports Paypal and these other combinations

  • Paypal with credit cards
  • Paypal with non credit cards
  • Paypal with any other electronic gateway

Paypal and VP-ASP 6.00

Our new release has included Paypal as a payment option by default. To integrate Paypal with your site, from within your site administration pages, go to Setup -> 6. Payments.

Locate the field xPaypal and set this to Yes.

Locate xPaypalEmail and insert your PayPal email address.

Next go to SetUp --> 4. Products 2

Locate xmysite and insert the path to your web site: http://www.yourvpaspwebsiteurl.com/

You will also need to modify the file paypalgateway.asp. Open this in any text editor, and change the lines at the top to suit your account: const

const CurrencyCode="USD" ' other values are EUR, CAD, GBP, JPY, USD

Paypal and VP-ASP (earlier versions)

To use Paypal, please download the Paypal Interface at www.vpasp.com/sales/epdownload.asp
VP-ASP allows the customer to purchase any number of goods at your shop. Paypal is just another payment method that you can elect to give to your customers.

VP-ASP also supports the new auto return feature of Paypal. Upon competition of the payment at Paypal, the customer is returns back to your site where VP-ASP updates the payment details (or checks them if using IPN) and then completes the order. If the customer cancels at Paypal, the customer can then an alternative payment method.

The URL for Paypal has changed. You may receive a warning message about an expired certificate when using the Paypal gateway code.

Depending on which Paypal interface you are using, edit paypalgateway.asp or a similar name (for VP-ASP 3.x name will be paypalshopcheckout.asp) and change

https://secure.paypal.com/cgi-bin/webscr
to
https://www.paypal.com/cgi-bin/webscr

Using Paypal IPN and other gateways

Using Paypal IPN with another gateway requires some minor changes to the instructions for installing Paypal. The steps are outline below.

1. First download the Paypal IPN interface from our downloads page.

2. Set up Paypal IPN by following the instructions that come with the zip file you receive. Just ignore the step that tells you to change the configuration option xcheckout.

3. Edit the current gateway file you are using. The example below is based on the default file shopcheckout.asp. If you are using Verisign, you would edit verisignshopcheckout.asp, etc.

4. Locate the following line -
!-- #include file="shopgateway.asp" -->

Add the following line below it -
!-- #include file="paypalipngateway.asp" -->

5. Locate the following line -

PerformGateway

Add the following line above it -

PayPalPerformGateway

Note: if you are using VP-ASP 6.00 or above, the line above may already exist and you will not need to make any changes.

6. Edit the file paypalipnresult.asp. Locate the following line -

backurl="paypalshopcheckout.asp"

Change to -

backurl="xxxxshopcheckout.asp"

Where xxxxshopcheckout.asp is the name of the file you edited in Step 2.

Troubleshooting Paypal

On some servers you may need to force Paypal to perform a POST back to the server your VPASP store is hosted on to successfully obtain the transaction information. If this is not done your transaction data may be blank on return from Paypal and you may also receive a Syntax error.

To implement this, you will need to make a minor adjustment to the paypalgateway.asp file.

Around line 40 locate:

<input type="hidden" name="cmd" value="_xclick" />

Immediately after this, insert a new row of code that reads:

<input type="hidden" name="rm" value="2">

This code forces Paypal to return its details as a form post rather than as a GET response and this should resolve any issues you have.

        

How to Fix and Debug Error With Authorize Net DPM Gateway for VPASP 7.00

If you are using Authorize Net DPM gateway and keep getting this error message :

Your credit card transaction failed
Please select another payment method
This transaction cannot be accepted

It could be related to your Authorize Net account settings.

There are some settings you need to check:

1. Login to your Authorize Net merchant at : https://account.authorize.net/
And then go to : ACCOUNT > click "Transaction Details API" link in the "General Security Settings" section.

2. Click the "Enable Transaction Details API" button.

3. After that, please also go to : ACCOUNT > click "API Login ID and Transaction Key" link in the "General Security Settings" section.
There you will see your API Login ID info e.g. : xxxxxxxxxxx

Please check the API Login ID showing there with the x_loginID value you already set in the file autconfig.asp. Both must be same :

const x_loginID = "xxxxxxxxxxx"

Also, while you are still at the API Login ID and Transaction Key page, please get a new transaction key in the "Create New Transaction Key" section.
Once you get a new transaction key, please put it into the x_transactionKey value inside the file autconfig.asp:

const x_transactionKey = "xxxxxxxxxxxxxxxxxxxxxx"

4. Next step is to check your account is in live mode or not.
Go to your Authorize Net merchant menu : ACCOUNT > click "Test Mode" link in the "General Security Settings" section.
If you see this : This account is currently in LIVE MODE, then your setting is already correct.
If your account is in test mode, make sure you turn it to live mode.

5. Go to your file autconfig.asp and make sure you have set to run in live mode :

const x_testMode = "false"


6. Save the file autconfig.asp and upload to your site.

After the above changes, you can try to checkout again using Authorize Net DPM gateway.

If you are still getting the same error msg as below :

Your credit card transaction failed
Please select another payment method
This transaction cannot be accepted


Then you will need to debug this more as the above error message does not specify what is the actual error response code returned by Authorize Net.

To debug, please follow these steps :

1. Open file autresult.asp using notepad or text editor.

2. Locate this code :

x_MD5_Hash = cleanchars(request("x_MD5_Hash"))


3. Directly below it, please insert this debugging code :

response.write "x_response_code = " & x_response_code & "<BR>"
response.write "x_response_reason_code = " & x_response_reason_code & "<BR>"
response.write "x_response_reason_text = " & x_response_reason_text & "<BR>"
response.end


4. Save the file and then upload to your site.

5. Run a test checkout again using Authorize Net DPM and you should see the actual error response code returned by Authorize Net e.g :

x_response_code = 3
x_response_reason_code = 251
x_response_reason_text = This transaction has been declined.


To getting know what is the error msg meaning returned in the x_response_reason_code, you can find out in the tool page below :
http://developer.authorize.net/tools/responsereasoncode/

In our example above, the x_response_reason_code showing 251. Please go to the tool page http://developer.authorize.net/tools/responsereasoncode/ and enter 251.
You should be displayed with information about error 251 like below :

Response Reason Code : 251
Response Reason Text : This transaction has been declined.
Integration Team Suggestions : This transaction was submitted from a blocked IP address.
Other Suggestions : The transaction was declined as a result of triggering a Fraud Detection Suite filter.

Based on the information as per example above, you should be able to determine and work out what causing it.

In the example above, it is clear that transaction declined related to Fraud filter.
In this case, you will need to check your Authorize Net merchant settings that related to Fraud filter.

Solution for the example above, can be as below:

1. Login to your Authorize Net merchant at : https://account.authorize.net/
And then go to : TOOLS > click "Fraud Detection Suite" link in the left sidebar.

2. Make sure you turn off / disable any fraud settings that causing the card payment to fail.
Please check any fraud filter and if they are no needed, you can turn them off e.g. :

- Enhanced AVS Handling Filter
- Regional IP Address Filter
- Amount Filter
etc...

3. Test again to checkout using Authorize Net DPM.

If the debugging msg returned something like below :

x_response_code = 1
x_response_reason_code = 1
x_response_reason_text = This transaction has been approved.

That means the payment is successful and you can take out the debugging code you have inserted earlier.

        

PayPal Payments Pro

How PayPal Payments Pro Works


See how easy it is for customers to pay for your products
and what makes PayPal a great choice.

Your Most Customizable Payments Solution

Fully customize your website checkout with this complete, [PCI-compliant]* payment solution. Customers can pay by credit card or PayPal without ever leaving your site, and you can tap into more than 100 million active PayPal users.

Ready to get started? Sign up Now

Features:

  • Accept credit cards and PayPal
  • Full customization options
  • Set-up is easy
  • No setup cost. $30 per month plus transaction fee.




Need help?

For questions or help getting started,email PayPal or call 1-877-455-1505.
        

PayPal Payments Standard

How PayPal Payments Standard Works


See how easy it is for customers to pay for your products
and what makes PayPal a great choice.

Accept PayPal and Credit Cards Securely

Add a PayPal payment button to your site to accept Visa, MasterCard®, American Express, Discover and PayPal payments securely. When your customers check out, they are redirected to PayPal to pay, then return to your site after they're finished

Ready to get started? Sign up Now

Features:

  • Accept credit cards and PayPal
  • Your customers don't need a PayPal account
  • Set-up is easy
  • You pay only when you get paid. (No set-up cost or monthly fees.)


Need help?

For questions or help getting started,email PayPal or call 1-877-455-1505.
        

PayPal Payflow Pro

Accept Payments with a Flexible Gateway

Connect a PCI-compliant payment gateway with your Internet merchant account to accept Visa, MasterCard, American Express, Discover and PayPal payments directly on your site. Payow Pro oers you complete control of your customers' payment experience and helps make sure every transaction is secure.

Ready to get started? Sign up Now

Features:

  • Accept credit cards and PayPal
  • Full customization options
  • One gateway for all banks
  • No long-term commitment or hidden fees


Need help?

For questions or help getting started,email PayPal or call 1-877-455-1505.
        

PayPal Payflow Link

Accept Payments with Your Merchant Account

Accept Visa, MasterCard®, American Express, Discover and PayPal payments on your site by connecting a PayPal-hosted checkout page with your own internet merchant account. Customize the page to look like the rest of your site and make sure customer transactions are secure.

Ready to get started? Sign up Now

Features:

  • Accept credit cards and PayPal
  • PCI-compliant gateway
  • One gateway for all banks
  • No long-term commitment or hidden fees


Need help?

For questions or help getting started,email PayPal or call 1-877-455-1505.
        

PayPal Express Checkout

How PayPal Express Checkout Works


See how easy it is for customers to pay for your products
and what makes PayPal a great choice.

Let Your Customers Pay with PayPal

Add PayPal as a payment method to your checkout page or use it as a stand-alone solution. You'll open the door to over 100 million active PayPal customers who look for and use this fast, easy, and secure way to pay.

Ready to get started? Sign up Now

Features:

  • Set-up is easy
  • Works for mobile websites and apps
  • You pay only when you get paid. (No setup cost or monthly fees.)You pay only when you get paid. (No setup cost or monthly fees.)


Need help?

For questions or help getting started,email PayPal or call 1-877-455-1505.
        

PayPal Payments Advanced

How PayPal Payments Advanced Works


See how easy it is for customers to pay for your products
and what makes PayPal a great choice.

Accept Payments Directly on Your Site

Add a PayPal payment button to your site to accept Visa, MasterCard®, American Express, Discover and PayPal payments securely. When your customers check out, they are redirected to PayPal to pay, then return to your site after they're finished

Ready to get started? Sign up Now

Features:

  • Accept credit cards and PayPal
  • Simplify PCI-compliance
  • Set-up is easy
  • No setup cost. $5 per month plus transaction fee.


Need help?

For questions or help getting started,email PayPal or call 1-877-455-1505.
        

Understanding Online Payments

In order to accept credit card payments online, you need:

1. An Internet Merchant Account (IMA)
2. A payment gateway

There are two methods for acquiring an IMA and a gateway. They are:

All-in-One Payment Solutions - IMA and gateway are bundled together

Payment Gateways - Mix and match your IMA and gateway

To attract customers who prefer not to use credit cards online, it's easy to offer alternate payment methods, such as PayPal. Typically all that’s required for this is an account with the service provider.

All-in-One Payment Solutions

With an all-in-one payment solution your IMA and gateway are acquired from a single vendor. This option is beneficial if you want to:

  • Manage just one vendor for all online payments
  • Get all of your support from a single source
  • Use easy-to-access reporting for all payment methods
  • Integrate only one application on your website

Payment Gateways

Payment gateways combine separate IMA and gateway providers. Consider this if you already have a physical store presence with IMA capabilities from your existing bank. A payment gateway allows you to:

  • Keep your existing IMA as you expand online
  • Connect a compatible gateway with your existing IMA
  • Retain the same gateway if you change IMA providers

Alternate Payment Methods

Because of credit card fraud and identity theft concerns, some customers are uncomfortable providing their credit card information on new websites or any that are unfamiliar to them. You can service those customers by accepting alternate payment methods like PayPal. With this option, many businesses—especially new or small businesses—find they can:

  • Increase sales on their site. Customers can select an alternate payments provider that they already trust.
  • Reduce shopping cart abandonment.
  • Add flexibility for their customers. Customers can pay without sharing personal and credit-card information with businesses.

For a full list of the Payment Solutions supported by VP-ASP, go to our Payment Gateways page.

 

Google Checkout

        

SSL Certificates supported

Only certain SSL certificates are supported by Google Checkout when it does a callback to the server to update your database.  While it is not essential to have a compatible SSL certificate, it does mean that your orders will be reported as "Canceled" because no "cardtype" is recorded for the order.  You will need to manually process the orders using Google's administration if you do not have a support SSL certificate installed. The current list of certificates supported are:
  • Baltimore Codesigning CA
  • Baltimore Cybertrust CA
  • Entrust 2048 CA
  • Entrust Client CA
  • Entrust Global Client CA
  • Entrust GSSL CA
  • Entrust SSL CA
  • Equifax Secure eBusiness CA1
  • Equifax Secure eBusiness CA2
  • Equifax Secure Global eBusiness CA1
  • Geotrust Global CA
  • Godaddy Class 2 CA
  • GTE Cybertrust 5 CA
  • GTE Cybertrust CA
  • GTE Cybertrust Global CA
  • Starfield Class 2 CA
  • Thawte Personal Basic CA
  • Thawte Personal Freemail CA
  • Thawte Personal Premium CA
  • Thawte Premium Server CA
  • Thawte Server CA
  • ValiCert Class 2 CA
  • VeriSign Class 1 CA
  • VeriSign Class 1 G2 CA
  • VeriSign Class 1 G3 CA
  • VeriSign Class 2 CA
  • VeriSign Class 2 G3 CA
  • VeriSign Class 3 CA
  • VeriSign Class 3 G2 CA
  • VeriSign Class 3 G3 CA
  • VeriSign Server CA 
        

Google Checkout does not callback in Live mode

As a requirement for Google Checkout, you need to have the callback script accessible via HTTPS.  However, it may not callback successfully due to a 401.1 error:
Unauthorized: Access is denied due to invalid credentials.
 
Please refer to your web hosting company of the following page for how to fix this issue:
http://blogs.msdn.com/david.wang/archive/2005/07/14/HOWTO_Diagnose_IIS_401_Access_Denied.aspx
 

PayPal Website Payments Pro

        

Paypal

The URL for Paypal has changed. You may receive a warning message about an expired certificate when using the Paypal gateway code.

Depending on which Paypal interface you are using, edit paypalgateway.asp or a similar name (for VP-ASP 3.x name will be paypalshopcheckout.asp) and change

https://secure.paypal.com/cgi-bin/webscr
to
https://www.paypal.com/cgi-bin/webscr         

PayPal Website Payments Pro Troubleshooting

Problem: I receive the following error when trying to submit a transaction to PayPal Website Payments Pro:

error '80131534'
/paypalproapi.asp, line 17

Solution: This error indicates that there is an issue with the registration of the Paypal DLL files.

Try the following steps to fix this problem:

1. Download the .NET v 1.1 SDK from Microsoft and install it.

2. Locate RegAsm and gacutil on your computer (use the Windows Search facility).
RegAsm.exe should be in the folder to where you installed the .NET Framework SDK
gacuti.exel should be in your .NET Framework directory

3) Add the path to gacutil and RegAsm to your system PATH (see this tutorial for more information on this).

4) Run the following commands on paypal_base.dll which is in the SDK/bin folder.

gacutil /i paypal_base.dll

regasm paypal_base.dll /tlb:paypal_base.tlb

5) Restart IIS.

6) Try checking out again.


Problem: Certain card types are failing with different error codes.

An issue you may encounter with Paypal Pro is that Visa cards work correctly but MasterCard and Amex (American Express) cards fail giving different errors.

American Express may fail with a 10504 error saying that the card validation number was not correct.

The MasterCard may fail with an error saying that the card number was not correct.

Solution: The resolution to both of these issues is to ensure that the xcreditcardtypes setting in your VPASP configuration settings has the correct values entered.

Valid values for use with Paypal Pro are Visa,MasterCard,Discover,Amex

They are case sensitive and must be exactly as shown above

 

Problem: I receive the following error when trying to submit a transaction to PayPal Website Payments Pro:

Your credit card transaction failed
Either retry it
or select another payment method
Result code = 10002 Security header is not valid

Solution: When switching from the sandbox to the live site - you will need to use your live PayPal account's API credentials - (username/password/signature).

You need to ensure that you have updated your credentials in paypalproconfig.asp so they reflect those of your Paypal live account.

See the following page from Paypal which explains that the production server will return this error for invalid account credentials:
http://paypaltech.com/Dave/api_sourcebook/html/Microsoft/Classic%20ASP/ASP%20Signature.html

        

PayPal Website Payment Pro Installation Guide for VPASP 7.00

PayPal Website Payment Pro is now built into VPASP 7.00 and above by default. Setting up PayPal Website Payment Pro is pretty straight forward, you simply need to enter your API Username, password and also signature to enable PayPal Website Payment Pro on your shopping cart.

The following guide will provide you a step by step guide on how to obtain your API credentials from PayPal and set the shopping cart up to use them.

How to obtain your PayPal API Username,Password and Signature

1. Log into your PayPal account.

2. Click Profile -> More Options.

3. Under the Account Information section, click API Access.

4. Click View API Signature on the left "Option 2" box.

5. Write down the API Username,Password and also the Signature. Once done, click the DONE button

How to Enable PayPal Website Payment Pro on VPASP 7.00

1. Log into your VPASP administration page.

2. Select Advanced Settings -> Software Configuration

3. Search for 'Paypal' (without the quotes) on the search box to the left.

4. Use the following configurations :

  • xPayPal_Website_Payment_Pro : Yes
  • xPayPal_API_UserName : Your API Username
  • xPayPal_API_Password : Your API Password
  • xPayPal_API_Signature : Your API Signature

5. Paypal Website Payment Pro is now enabled !

Other Issues

If you have questions or issues with the latest PayPal Website Payment Pro, please submit a ticket to our helpdesk at https://helpdesk.vpasp.com         

PayPal Express Checkout Installation Guide for VPASP 7.00

PayPal Express Checkout is now built into VPASP 7.00 and above by default. Setting up PayPal Express Checkout is pretty straight forward, you simply need to enter your API Username, password and signature to enable PayPal Express Checkout on your shopping cart.

The following guide will begin with a brief explanation of what API credentials are, followed by a step by step guide on how to obtain your API credentials from PayPal and set the shopping cart up to use them.

What are API credentials?

Application Programming Interface (API) is the way in which two programs communicate with each other. To put it simply, it is like a phone call between two computers. In the case of PayPal API’s, scripts on your ecommerce store send an API ‘call’ to PayPal’s servers asking PayPal to do something for your site (e.g. accept a payment).

API Credentials are the information sent to PayPal to identify who is making the request, similar to caller ID on a phone call.

PayPal's API credentials consist of an API username and password (not the same ones you use to log in to paypal.com), as well as a third piece of information - either a signature or a certificate. You only require one of either a signature or a certificate, they both serve the same purpose. With your VP-ASP store you will use the signature method.

How to obtain your PayPal API Username,Password and Signature

1. Log into your PayPal account.

2. Click Profile.

3. Next, click 'My Selling Tools'.

4. Now locate 'Manage API Credentials to integrate my PayPal account with my online store or shopping cart' and click 'Update'

5. If you have never requested API credentials from your PayPal account, you'll see a 'Request API credentials' link in the Option 2 box, click it.

6. Select 'Request API signature' then click 'Agree and Submit.

7. Your API Username,Password and Signature will now be displayed, write them down then click the 'Done' button

How to Enable PayPal Express Checkout on VPASP 7.00

1. Log into your VPASP administration page.

2. Select Advanced Settings -> Software Configuration

3. Search for 'Paypal' (without the quotes) on the search box to the left.

4. Use the following configurations :

  • xPayPal_Express_Checkout : Yes
  • xPayPal_API_UserName : Your API Username
  • xPayPal_API_Password : Your API Password
  • xPayPal_API_Signature : Your API Signature

5. Paypal Express Checkout is now enabled !

Other Issues

If you have questions or issues with the latest PayPal Express Checkout, please submit a ticket to our helpdesk at https://helpdesk.vpasp.com        

How to Set up Paypal Website Payments Hosted Solution Using an Iframe

In this helpnote, we will guide you through setting up Paypal's Website Payments Hosted Solution to use an iframe in your VP-ASP store's checkout page.

NOTE :
Paypal Website Payments Solution is not available in the United States. The table below shows which countries are compatible, the solution name may vary from country to country but it is the same solution.



The Paypal Hosted Solution is a great module to integrate with your VP-ASP store as it allows your customers to remain on your site when checking out.

This is made possible by using an iframe to pull code from the Paypal site while your customers still see your front store layout.

Below is an example of this solution:


With the Hosted Solution, your customers have two options in the same form. They can choose to pay using "Pay with Paypal" button in the top section or they can enter their credit card number into the bottom section.

To set up Hosted Solution, please follow the steps below:

1. Login to your VP-ASP store admin and go to: Advanced Settings » Software Configuration.

2. Search for : xpaypal

3. Enter the value for the configs below :
xPaypal Yes
xPayPal_API_Password Enter your PayPal API Password here
xPayPal_API_Signature Enter your PayPal API Signature here
xPayPal_API_UserName Enter your PayPal API user name here
xpaypal_MERCHANT Enter your Paypal merchant id here.
You can find your Paypal Merchant id by login to Paypal site : https://www.paypal.com/webapps/mpp/merchant, and go to menu : My Account --> Profile.
xPayPal_Test_Mode No
xPayPal_Website_Payment_Pro No
xPaypalEmail Enter your paypal email address

4. Click Continue once the above configs are set.

5. Download this zip file paypalhosted700.zip.

6. Unzip and upload the files below to your VP-ASP site at the root:

- shopgateway.asp
- paypalhostedgateway.asp
- paypalhostedresult.asp

Make sure you make a backup of your existing file shopgateway.asp.

7. The last step is to login to your Paypal merchant account at https://www.paypal.com/webapps/mpp/merchant, and go to: My Account --> Profile.

Turn on the Auto Return setting, enter http://www.yoursite.com/paypalhostedresult.asp into the Return URL field and turn on Payment Data Transfer as shown below:

Note : Replace the www.yoursite.com with your VPASP site url.



You are done!

Here's an example of the Paypal Hosted Solution integrated into a VP-ASP store:



Note : You can change the iframe width and height to fit your site layout by editing file paypalhostedgateway.asp (line 65) :

<iframe name="hss_iframe" width="525px" height="460px" frameborder='0'></iframe>

Replace 525px and 460px with your own size.

If you have any issues during implementation of the steps above, you can submit a ticket to our helpdesk and our support team will assist:
https://helpdesk.vpasp.com

        

Introduction to PayPal Website Payments Pro

VP-ASP is proud to announce its integration with PayPal Website Payments Pro. USA users can now accept credit card payments directly on their website; allow PayPal account holders to check out fast with saved information; get industry-leading security; take advantage of comprehensive online reports.

Download PayPal Website Payments Pro now!


With VP-ASP and PayPal Website Payments Pro you can be assured that your e-commerce solution will be:

Powerful. VP-ASP directly integrates with PayPal Website Payments Pro, allowing you to control your checkout from start to finish.

Complete. Accept credit cards directly on your website (just like a merchant account!). With VP-ASP and the PayPal Website Payments Pro gateway you don’t need a separate merchant account and gateway.


VP-ASP brings you the advanced features of PayPal Website Payments Pro completely integrated into your shopping cart! Take advantage of:

Accepting credit card payments directly on your website; PayPal processes payments in the background, so you control the customer experience.

Allowing PayPal accountholders to check out fast with saved information, plus, gain incremental sales from PayPal’s growing base of more than 100 million user accounts in 55 countries and regions.

Get industry-leading security. With VP-ASP’s anti-hacker security and fraud controls combined with PayPal’s industry-leading fraud-prevention systems in place you can rest assured that your online store is safe and secure. Plus, you can control your level of risk—to allow only the types of transactions you prefer.

Take advantage of comprehensive online reports from VP-ASP and PayPal that help you measure sales and manage your business easily.

        

Issue with the Other Payment form when using the built-in PayPal Pro module

If you are using the built-in PayPal Website Payment Pro (paypalprodpshopcheckout.asp) and receive an error when selecting an "Other Payment" while leaving the "Comment Box" empty, the following fix will need to be applied to paypalprodpshopcheckout.asp

1. Open the file "paypalprodpshopcheckout.asp" using a text editor and locate the following code:

(Approximately located on line 331)
paymenturl=""

2. Now, add the following code below :

if stromore = "" then
stromore = "-"
end if

        

PayPal Website Payments Pro Installation


Please note ! This helpnote is now outdated. If you are using VPASP 7.00, please use the following guide.




There are two methods to interface with Paypal - API Certificate or 3-token Authentication. There are several requirements that you need before you can use PayPal Website Payments Pro.

1. Both methods require that the DLL and TLB files included in your download (paypal_base.dll and paypal_base.tlb) to be registered with your server.

2. You need to install certificates on your server - you need to check with your host to see if they will allow you to have these installed.

3. If you wish to use Direct Payment, you will also need your own SSL certificate.

4. You need to apply for a Business account with PayPal - you can do this at PayPal's website.


Download the Paypal Pro SDK Installation Guide


Registering the Paypal_Base

If your website is in a shared hosting environment, your web hosting company will need to follow these steps to register the files.

1. Locate RegAsm and gacutil on the server machine
- RegAsm.exe should be in the folder to where the .NET Framework SDK.
- gacuti.exel should be in the .NET Framework directory

2. Add the path to gacutil and RegAsm to your system PATH.

3. Run the following commands where paypal_base.dll and paypal_base.tlb files are located

gacutil /i paypal_base.dll
regasm paypal_base.dll /tlb:paypal_base.tlb

Setting up in Paypal

1. Log into Paypal, go to Profile->API Access
2. Click Get Started in the Request API Credentials box
3. Choose either API certificate file for download or API signature for three-token authentication
4. Select checkbox to agree to Paypal's terms & conditions
5. Click Submit
6. Click Download Certificate, if applicable
7. If you are using API certificates, please refer to PayPal's website for information on how to obtain and install the certificate.


Setting up in VP-ASP

1. Enter the details given in paypalproconfig.asp:

For API Certificate-
Const API_USERNAME = "API User Name"
Const API_PASSWORD = "Password"
Const API_SIGNATURE = ""
Const CERTIFICATE = "Certificate Name"

For 3-token authentication-
Const API_USERNAME = "API User Name"
Const API_PASSWORD = "Password"
Const API_SIGNATURE = "Signature Hash"
Const CERTIFICATE = ""

2. Update VP-ASP Set-Up configurations
xcheckout="paypalproshopcheckout.asp"

Configuration
The following variables can be configured in paypalproconfig.asp file:

const ENVIRONMENT="sandbox" or "live"
Set to sandbox when testing, or live for live transactions

const OverwriteShippingAddress="No" or "Yes"
For customers using Express Checkout, they will already have an existing shipping address, set to "No" if you don't want the customers to overwrite the shipping address.

Leave the following settings, as only US Business accounts are allowed at this time
const CommaAsDecimal="No"
const ConvertToUS="No"
const ResetLcid="1033"
const CurrencyCode="USD"

Testing
Paypal requires you to sign up to their Sandbox facility for testing. The sandbox is essentially a copy of the real one, but certain activities (such as transactions and emailing) are not live.

It is recommended that you create two accounts- one Business account to test as the merchant, and one Personal account to test as a customer.

Please go to the following URL to create a sandbox account https://developer.paypal.com/

Results
When your customer finishes shopping, they will be directed to paypalproshopcheckout.asp. They will see a Checkout with Paypal button as well as a payment form.

After completing payment they will be directed back to your site to either paypalprodirectresult.asp or paypalproexpressresult.asp.

The status will be stored with the order and they will be directed to shopthanks.asp where normal invoice is printed and emails sent.

The ocardtype will be set to PaypalPro. This will tell you that payment was done through PayPal Website Payments Pro.

Other VP-ASP Settings

To remove the normal VP-ASP credit card form, open paypalproshopcheckout.asp and change the following:

AllowCreditCards="No"

To disallow other payments set

AllowOtherPayment="No"

 

SSL

        

SSL

Secure Sockets Layer (SSL) technology encrypts information from a customer PC to your web site. SSL is implemented using what is known as digital certificates that bind an identity to a pair of electronic keys that can be used to encrypt and sign digital information.

A Secure Server ID makes it possible to verify someone's claim that they have the right to use a given key, helping to prevent people from using phony keys to impersonate other users. Used in conjunction with encryption, Secure Server IDs provide a complete security solution, assuring the identity of one or all parties involved in a transaction.

More information at: http://digitalid.verisign.com/server/about/aboutFAQ.htm

When don't I need SSL?
If you are planning to use an electronic banking gateway that takes the customers credit card information at their own site, then you don't need SSL on your own web host. When the person gets to the point of needed to enter payment information, the button goes of to an SSL protecting electronic gateway. 

VP-ASP supports many of the most popular electronic gateways See our description of electronic gateways.

Do I Need SSL?
Maybe. 
If you are planning to take credit card information using standard VP-ASP facilities then yes you probably do. Internet buyers will only trust their credit card if they know it is securely transmitted.
But you may not need to buy a digital certificate. Many web hosting companies let you use their digital certificate for free or for a small charge. Check with you web hosting company.

Configuring VP-ASP to use SSL


If you are planning to use SSL on you web site with VP-ASP, here are some tips.
For VP-ASP  change the shop configuration value

xssl=https://yourweb.com/shopping

It must have https to use SSL encryption

Can my SSL be on a different Server?

A "secure server" is an invention of your web hosting company. It is a way to use an SSL certificate without actually buying one. Every web hosting company that supplies a "Secure Server" facility does it differently.  Please read our information on Shared SSL.

        

Where do I get SSL

SSL certificate is something you purchase from third parties such as Thawte or Verisign. If you have your own SSL certificate, then you can configure VP-ASP to use it. VP-ASP also supports shared SSL. Shared SSL is where your web hosting company provides an SSL certificate for you.         

Do I need SSL

Maybe!

If you are planning to take credit card information using standard VP-ASP facilities then yes you probably do. Internet buyers will only trust their credit card if they know it is securely transmitted.

But you may not need to buy a digital certificate. Many web hosting companies let you use their digital certificate for free or for a small charge. Check with your web hosting company.         

When you don't need SSL

If you are planning to use an electronic banking gateway that takes the customers credit card information at their own site, then you don't need SSL on your own web host. When the person gets to the point of needing to enter payment information, the button goes to an SSL protecting electronic gateway. VP-ASP supports many of the most popular electronic gateways.         

SSL and VP-ASP

If you are planning to use SSL on your web site with VP-ASP, here are some tips.

1. Edit VP-ASP configuration and change the following statement

Xssl

https://yourweb.com/shopping

It must have https to use SSL encryption         

SSLShopCheckout -Web Hosting Companies SSL on another Server

Some web hosting companies allow you to use their security certificate but sometimes it is on a totally different server. This is called “shared SSL”. Shared SSL is an invention of your web hosting company and every web hosting company implements this uniquely. For this reason VP-ASP requires special handling if you plan to use “shared SSL”.         

Shared SSL Restrictions

What is Shared SSL? A "secure server" or "shared SSL" is an invention of your web hosting company. It is a way to use an SSL certificate without actually buying one. Every web hosting company that supplies a "Secure Server" facility does it differently. VP-ASP only supports this shared SSL to take credit cards using our special sslshopcheckout.asp. This is true whether the "shared ssl" is just a separate folder on the same server or on another sever entirely.

Because this "secure server" is unique to your web hosting company, some of our electronic gateway interfaces can use it. Our forms based gateways may not work but our COM based gateways will work if certain special procedures are followed.

VP-ASP supports this 'secure server" facility only with our special SSLshopcheckout interface.

With a Shared SSL certificate you cannot:

  • Use any of our supplied gateways
  • Use the VP-ASP Admin system in SSL Mode
  • Use any other VP-ASP files in SSL Mode
  • It can only be used to store credit card details in the VP-ASP database for manual credit card processing.
  • Language switching is not supported         

    Using SSL ShopCheckout

    To allow the SSL to be on a different server (or a different folder on the same server), we have created an interface called sslshopcheckout.asp. This code is allows you to take credit cards using a server with SSL using "shared SSL". This interface does require a number of VP-ASP files to be placed in your secure server. The database does not need to be copied.        

    Configuring Shared SSL

    Your web hosting company must allow you to install a few files on this “Secure Server”. VP-ASP has a special interface called sslshopcheckout.asp that needs to be installed on the “secure server”. The steps are:

    •  Alter VP-ASP Configuration

    Xssl

    https://yourwebhostsotherserver.com/yourdirectory

    Xcheckout

    sslshopcheckout.asp

    Copy the Following Files to the secure server.

    sslshopcheckout.asp
    sslshophash.asp
    sslshopsess.asp
    shop$language_english.asp
    shop$colors.asp
    shop$config.asp
    shop.css

    •  Edit SSLshopcheckout.asp

    Change these two lines

    const MYSITE="http://www.YourSite.com/shopping"

    const xEncryptkey="agabAhjBcG"

    The first line points back to where VP-ASP is installed on your main site.
    The second is the encryption key. It must match the xencryptkey in your VP-ASP configuration.

    •  SSL ShopCheckout Configuration

    Since SSLshopcheckout could be on a server different from the one the VP-ASP shop is on, the normal Shop Configuration Values do not apply. This means that if you wish to change credit card types, turn on or off the Card Verification Number display, turn on an issue number, then all these must be done by altering one or more lines in sslshopcheckout.asp. These lines are near the top of sslshopcheckout.asp

    const CVNDisplay="Yes"

    Display prompt for Card Verification number

    const CVNRequired="No"

    Whether CVN is required

    const xEncryptkey="agabAhjBcG"

    Encrypt key.. Must match your shops encryption key

    Const MYSITE="http://www.yourshoppingsite.com/shopping"

    Location where normal shop resides

    Shop$language_English.asp

    Change this to your normal language file

    •  Configure Credit Cards

    For example if you take Diners and Bankcard but not American Express the list would look like this:

    Const Creditcards="Visa,Mastercard,Diners Club”

    •  Configuring Non-Credit Cards

    There is an array of non credit card payment types. Suppose you want to remove cash and add Purchase Order and Fax Order.

    Const Otherpayments="Check,Purchase Order, Fax Order,Phone Order"         

    What VP-ASP does with SSL

    All that VP-ASP does is switch between non secure mode and SSL mode when invoking page shopcheckout.asp. This is where credit card information is entered. It does this by concatenating what you placed in xSSL in the configuration file with the filename shopcheckout.asp to create a full URL in the form:

    https://yourweb.com/shopping/shopcheckout.asp         

    Where are my normal headers and footers

    Because the sslshopcheckout.asp could be on another server, we have tried to make it easy to install. If you wish to add more information or additional headers or images, you will need to modify sslshopcheckout.asp

    You would add additional HTML in these two subroutines

    Sub NewShopPageHeader
    %>
    html>
    head>
    title>Shopping Cart Secure Checkout/title>
    link rel="stylesheet" href="shop.css" type="text/css">
    /head>
    body bgcolor="#FFFFFF" text="#000000" link="#BB0000" vlink="#000099" alink="#336699">
    center>
    %
    end sub
    Sub NewShopPageTrailer
    %>
    /body>
    /html>
    %
    End Sub

            

    Shared SSL Enhancements

    Shared Enhancements
     
     
    The shared SSL enhancement allows certain (but not all) gateways to be used in a shared ssl environment.

    The extension allows COM based gateways to use shared SSL. A COM based gateway is any gateway interface that does not actually leave your site. Examples of these include:

    • Verisign Payflowpro
    • Authorizenet AIM
    • Linkpoint COM wrapper
    • Echo COM
    • and many others

    For more information on shared SSL, please click here

    Using SSL Enhancement
     

    The enhancement involves using an updated file called sslresult.asp and a new file called ssldecline.asp.

    • Download and install the SSL enhancement code if needed
    • Follow instructions in Developer's Guide for installing SSLshopcheckout.asp. This is section 32.4 of the VP-ASP 5.0 Developer's Guide
    • Change the normal install instructions for the gateway that would normally say something like set Shop Configuration
      xcheckout=pfpshopcheckout.asp
      you make this
    • xcheckout=sslshopcheckout.asp
      xpaymenturl=pfpshoppayment.asp
    • The payment file is totally dependent on the gateway. Each gateway has a different name. For example it may be anaimshoppayment.asp
    • An alternative to xpaymenturl is to actually edit sslresult.asp and change. It is your choice as to which is easier for you.
      Forwardurl="pfpshoppayment.asp"
    • Change where to go in case the credit card is declined.
      Edit the pfpshoppayment.asp. The file name is the same as entered in the xpaymenturl above and is dependent on the gateway you are using. For example it could be anaimshoppayment.asp etc.
    • backurl="anaimshopcheckout.asp"
      and change to
      backurl="ssldecline.asp" 

    How it works
     

    • The customer shops normally.
    • When they come to enter their card details they go to sslshopcheckout.asp on the "secure server"
    • On return they go to sslresult.asp. It decides whether the gateway code should be called by looking at the xpaymenturl.
    • The gateway code (say Verisign PayflowPro), then validates the credit card
    • If the card is successful the shopping completes normally
    • If the card fails, ssldecline.asp is called. It displays why the card failed and gives the customer a chance to try again or cancel the order.

    How do you know if it works
     

    If you run a test and you put in the credit card details in sslshopcheckout.asp and if you put in an invalid card and error message appears in file ssldecline.asp, then it is working.

    For a real card, VP-ASP should automatically direct to file shopthanks.asp and the payment type should be the name of your gateway such as Verisign or Authorizenet etc.
     

            

    SSL enhancements for COM based gateways

    To support Com based gateways and shared SSL, you must use a combination of sslshopcheckout.asp and the gateway interface we supply. Suppose you want to use Verisign Payflowpro. This gateway normally requires that you have your own SSL certificate. VP-ASP allows you to use this gateway with our shared SSL code. But this requires that you do the following extra steps:

    First install the gateway as per the instructions that come with the gateway interface that we supply.

    1. Change the normal install instructions for the gateway that would normally say something like set Shop Configuration

    xcheckout=pfpshopcheckout.asp
    you make this
    xcheckout=sslshopcheckout.asp
    xpaymenturl=pfpshoppayment.asp

    The payment file is totally dependent on the gateway. Each gateway has a different name. For example it may be anaimshoppayment.asp. What the above does is to first use the sslshopcheckout facility to collect the credit card details and then use the actual gateway interface to process the credit card.

    An alternative to xpaymenturl is to actually edit sslresult.asp and change. It is your choice as to which is easier for you.

    Forwardurl="pfpshoppayment.asp"

    Next change where to go in case the credit card is declined. Edit the pfpshoppayment.asp. The file name is the same as entered in the xpaymenturl above and is dependent on the gateway you are using. For example it could be anaimshoppayment.asp etc.

    backurl="anaimshopcheckout.asp"

    and change to

    backurl="ssldecline.asp"

    • How it works

    The customer shops normally. When they come to enter their card details they go to sslshopcheckout.asp on the "secure server" On return they go to sslresult.asp. It decides whether the gateway code should be called by looking at the xpaymenturl.

    The gateway code (say Verisign PayflowPro), then validates the credit card.

    If the card is successful the shopping completes normally.

    If the card fails, ssldecline.asp is called. It displays why the card failed and gives the customer a chance to try again or cancel the order.

    • How do you know if it works

    If you run a test and you put in the credit card details in sslshopcheckout.asp and if you put in an invalid card and an error message appears in file ssldecline.asp, then it is working.

    For a real card, VP-ASP should automatically direct to file shopthanks.asp and the payment type should be the name of your gateway such as Verisign or Authorizenet etc.

            

    Switch Customer Registration page in HTTPS (For VPASP 6.50 and 7.00)

    If you have changed the shop$config.asp file and updated Xssl to use HTTPS url of your site and changed xsslshopcustomer config to Yes, and you still see that the customer registration page (shopcustregister.asp) is still not in HTTPS, then you can follow these steps below to make it displays as HTTPS:

    1. Open the file shopcustregister.asp using notepad or text editor.

    2. Locate this code :

    <!--#include file="shopmailformattemplate.asp"-->


    3. Directly below it, please add this code :

    <%
    Response.Buffer = True
    If (Request.ServerVariables("HTTPS") = "off") Then
    Dim xredir__, xqstr__

    xredir__ = "https://" & Request.ServerVariables("SERVER_NAME") & _
    Request.ServerVariables("SCRIPT_NAME")
    xqstr__ = Request.ServerVariables("QUERY_STRING")

    if xqstr__ > "" Then xredir__ = xredir__ & "?" & xqstr__

    Response.redirect xredir__
    End if
    %>

    4. Save the file and upload your site.

 
Back Printable Version Search other topics Submit a Ticket