Entries Tagged 'Payment Integration' ↓

1) Problem: Getting an error that looks like this after purchase – using 1-Click Upsells.

Warning: file_get_contents(/home/mysite/dap/upsell1.html) [function.file-get-contents]: failed to open stream: No such file or directory in /home/mysite/dap/continue.php(1) : eval()'d code on line 20


Solution: Create missing file.

Every buy button generated by DAP for Auth.net or Paypal Payments Pro, will look something like this…

<form name=”generate_authnet” method=”post” action=”https://www.DigitalAccessPass.com/dap/buy.php”>
<input type=”hidden” name=”item_name” value=”DAP Upsell Tree – Auth.net (T)”/>
<input type=”hidden” name=”description” value=”DAP Upsell Tree For Authorize.net” />
<input type=”hidden” name=”amount” value=”97.00″ />
<input type=”hidden” name=”trial_amount” value=”0.01″ />
<input type=”hidden” name=”total_occurrences” value=”1″ />
<input type=”hidden” name=”is_recurring” value=”Y” />
<input type=”hidden” name=”recurring_cycle_1″ value=”365″ />
<input type=”hidden” name=”recurring_cycle_2″ value=”365″ />
<input type=”hidden” name=”recurring_cycle_3″ value=”365″ />
<input type=”hidden” name=”payment_succ_page” value=”https://www.YourSite.com/dap/continue.php?url=/dap/upsell1.html” />
<input type=”hidden” name=”payment_gateway” value=”authnet” />
<input type=”hidden” name=”is_submitted” value=”Y” />
<input type=”submit” value=”Buy Now” />
</form>

If you see the line in bold above, you will see the field…

payment_succ_page

… pointing to the first upsell…

https://www.YourSite.com/dap/continue.php?url=/dap/upsell1.html

What this essentially means, is that once the payment for the front end order is complete, you want the contents of the page /dap/upsell.html to be presented as the first upsell.

So…

a) Either create an HTML page called upsell1.html in the dap folder.

b) Or change the name of the file in the buy-button form code above, to be whatever your actual file name is.

c) Or if you don’t wish to do any upsells, then put the URL of your final thank you page in that field’s value.

2) Question: How do I use my own button with the shopping cart script?

Look for this in the DAP generated button code:
input type=”submit” value=”Buy Now”

Replace it with your own image :
For example –
input type=”image” src=”/images/btn-order.png” value=”Buy Now”

If images folder is at the root of your site, set src = /images/btn-order.png. If it’s under dap folder, the src tag should be set to “/dap/images/btn-order.png”.

There really is no one-size-fits-all when it comes to refund policies.

There are so many factors involved. The main one being, that Visa/Master/Amex/Paypal all give a buyer up to 60 days to ask for a refund, at least with most merchants.

Unless you’ve already negotiated the refund terms with your merchant account provider, and have both specifically agreed that there would be no refunds (like say, if you were selling an expensive item, like a car, or a boat, or a service), or that it’s only going to be a 30-day refund period, then you really have no control over the refund period. You just have to comply with at least the mandatory 60-day refund period required by the credit card companies.

So that brings us to the question:

How much should you set your refund period to be within DAP?

Now remember, it is this Refund Period setting (under Setup > Config > Advanced) that also makes affiliates eligible for payment.

So it really comes down to the question:

What is the waiting period for an affiliate to get paid for a referral?

Our recommendation: 60 days.

That’s because if you end up paying too soon (say like within 15 or 30 days), and then the buyer comes back and asks for a refund, now you’re out-of-pocket for the affiliate commissions that you have already paid on a purchase that you just refunded.

Now remember that when you do the actual refund within DAP, DAP will roll-back any commissions credited towards this purchase. If you have not yet paid your affiliates, then in the next report, it will ignore the refunded purchase, and will not calculate commissions on that purchase.

But if you have already paid your affiliates (like within 15 or 30 days after purchase), then DAP will include the negative commission in the next pay-period’s report. And any future commissions earned by this affiliate will be accordingly adjusted.

However, if the affiliate doesn’t refer any more members, then you have two choices at this point:

1) Ask the affiliate to pay back the over-paid commissions

2) Just swallow the loss, write it up to the cost of doing business, and move on.

Customer Flow

1. Buyer comes to your web site and clicks on your buy button and is taken to e-junkie to checkout
2. Buyer finishes paying, and then they are redirected to a static page on your site that says something to the effect of “Thank you for your purchase. Please check your email id that you just used during purchase, for information about how to login and access the product you just purchased.”
3. While this is happening, in the background, e-junkie would’ve already notified DAP via their back-end notification process called “Common Notification”, and DAP would’ve already created an account for the buyer, and emailed the buyer the login details.
4. Buyer checks their email id, and they see the email from you giving them their login details.
5. They login to your site using that information.

That’s the big picture. Now for the specifics on how to integrate DAP & e-Junkie.

E-Junkie Integration with DAP

1) Create a product in DAP that you want to be able to sell via e-junkie
2) Create a product in e-junkie with exactly the same name as the DAP Product name, and create a buy button for it.
3) Go to the e-junkie Seller Admin > Edit Account Preferences > Common Notification URL field
Set it to point to…

http://yoursite.com/dap/dap-ejunkie.php
(replace yoursite.com with the name of your site)

4) Go back to DAP Setup -> config -> payment processing section.
Look for these config items:

Merchant’s Payment Gateway API Login ID
Merchant’s Payment Gateway Transaction Key

And set these to match your ejunkie merchant login Id and password. This is needed for security validation.

That’s it!

Go ahead and test your purchase and see if it makes it to DAP Payment/Coupons => Orders page and if the users get added.

NOTE:

Please note that even though the DAP/Infusionsoft integration code is built right into DAP, and there’s no additional charge for the feature itself, however, support for this feature is not free, and is not part of the Standard DAP support you get with your purchase of DAP. We receive support tickets from Infusionsoft users not setting up their Infusionsoft account correctly, and we end up having to work on their Infusionsoft accounts for reasons completely unrelated to DAP, something for which we are not responsible for. So if you want us to support any questions or problems related to the DAP/Infusionsoft integration, we will have to charge you for it. Please contact us for details about how to purchase support time.

a) For Free products, you can use infusionsoft opt-in form on your squeeze page and integrate it with dap.  You have to set the action trigger upon opt-in (within infusionsoft) to point to http://yoursite.com/dap/dap-infusionsoft-optin-productID.php

NOTE: Replace productID with the actual DAP product Id.  So if you want to integrate a DAP product with the DAP product ID = 10 with Infusionsoft, then copy /dap/dap-infusionsoft-optin.php to /dap/dap-infusionsoft-optin-10.php.  Change $default_product_id to 10 in the dap-infusionsoft-optin-10.php script. Upload script to dap folder on your site. Set the web form action trigger within infusionsoft to point to http://yoursite.com/dap/dap-infusionsoft-optin-10.php (replace yoursite.com with the name of your site).  Also do steps 1 thru 3 below to complete infusion=>dap integration.  That’s it.

b) For paid products,  you can use infusionsoft shopping cart and integrate it with dap as described below. You can setup action sets in Infusionsoft to trigger http post notifications to DAP upon every purchase of a program or a product.  The notification to DAP will result in membership account getting created in DAP. You can use InfusionSoft as the shopping cart and DAP to manage members, drip and protect content.

Here’s a summary of the installation procedure, so you have it handy in case you want to use it.

1) Download the Infusionsoft Software Development Kit (PHP iSDK package) from http://developers.infusionsoft.com/sdks/

2) Extract the contents of the zip file. Upload the iSDK/src/xmlrpc-3.0 folder into the DAP folder on your site (via FTP), as well as the following 2 individual files: conn.cfg.php and isdk.php directly to the dap folder on your site.

If you uploaded it correctly, you should see a folder called xmlrpc-3.0 under /dap folder on your site.

You should also see conn.cfg.php and isdk.php under dap folder on your site.

3) Update the following file before uploading: conn.cfg.php. This needs to have the Infusionsoft API code and application name added for your infusionsoft account.

<?php

$connInfo = array(‘connectionName:applicationName:i:[API_code_goes_here]:This is the connection for applicationName.infusionsoft.com’);

?>

Here,
connectionName = demo
applicationName = <Set to your Infusionsoft Application Name>
[API_code_goes_here]  = Go to Setup – > Misc. Setting -> go to Miscellaneous tab -> Enter an api passphrase and hit Save.
It will generated an encrypted API Code. Replace [API_code_goes_here] with the api code.

The connectionName needs to be hardcoded to “demo”.

For ex:   I have used the applicationName of “veena” below.

<?php

$connInfo = array(‘demo:veena:i:dd2ebm098bsasghf68ihk:This is the connection for veena.infusionsoft.com’);

?>

4) Login to your infusionsoft account:

a) Go to Setup -> application Settings -> Misc -> Incoming action set (Add)

Select “Send an HTTP Post to Another Server” action set and set it to point to :
http://yoursite.com/dap/dap-infusionsoft.php (replace yoursite.com with the name of your site), then click Save.

b) Go To Setup -> Ecommerce -> Purchase actions -> Successful Purchase Action

Select “Send an HTTP Post to Another Server” action set and set it to point to :
http://yoursite.com/dap/dap-infusionsoft.php (replace yoursite.com with the name of your site), then click Save.

c) Go To Setup -> Order forms-> select the product -> Click on action Success tab  -> Add New Action->

Select “Send an HTTP Post to Another Server” action set and set it to point to :
http://yoursite.com/dap/dap-infusionsoft.php (replace yoursite.com with the name of your site), then click Save.

5) Make sure your product names in Infusionsoft exactly match the ones you have set up in DAP.

That’s it.

DAP supports 3 different types of Paypal Integration.

1) Paypal Hosted Buttons
2) DAP Generated Buttons For Paypal
3) DAP Shopping Cart with Upsells

Let’s get into more details about each one of them.

1) Paypal Hosted Buttons

You generate the button within your Paypal account.

Click Here to find instructions to integrate DAP and Paypal Hosted Buttons.

If the integration is not working, Click Here to find troubleshooting instructions.

Note: you only need to set the following config items for Paypal hosted buttons.

a) If you want to use Paypal Sandbox for testing, then set the following to “Y”.
DAP Setup -> Config -> Paypal -> Use Paypal Sandbox: For initial testing only

If you want to connect to your Paypal live account, then set it to “No”.

b) If your site has trouble connecting to Paypal via CURL and you see this error in DAP orders page => Check Product and Price(Reprocessible), then update the config below to FOPEN.

DAP Setup -> Config -> Paypal -> 4) Paypal Communication Protocol: How DAP connects to and communicates with Paypal on the back-end.

That’s it.

The following config items are NOT needed if you use the Paypal hosted buttons.

Paypal API Username - Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Password - Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Signature – Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Endpoint - Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.

Paypal Business Email ID - Only needed if you use the DAP generated button for Paypal (DAP Payments/Coupons -> Generate paypal button)

Merchant Payment Gateway API Login ID: Only needed if you use e-junkie or the DAP upsell tree plugin for Authorize.net
Merchant Payment Gateway Transaction Key: Only needed if you use e-junkie or the DAP upsell tree plugin for Authorize.net

The following fields in the DAP Products page ONLY need to be set if you use DAP upsell tree plugin or the DAP generated button for Paypal.

Recurring Count, Trial Amount and Product Price

If you are using regular paypal button, you can leave these empty. Even if these are not-empty, DAP will not use it for regular paypal hosted buttons.

2) DAP Generated Buttons For Paypal

With DAP 4.0, we have added support for DAP generated buttons for Paypal. You no longer have to generate buttons within Paypal.

You can generate the button for Paypal from within your DAP Admin Panel -> Payment Processing -> Generate Paypal Button page.

Click Here to find instructions to integrate the DAP generated button with Paypal.

3) DAP Shopping Cart / DAP Upsell Tree Plugins

1) Paypal Standard Upsell Tree Plugin
2) Paypal Payments Pro Upsell Tree Plugin / DAP shopping cart

Click Here for details.

DAP Supports Login Xpress with 1ShoppingCart (What is Login Xpress?)

The documentation below will show you how to setup 1ShoppingCart and DAP, so that your buyers can be automatically logged in to your “Member’s Area” upon completion of their purchase.

Note About Processing Recurring Orders via 1SC

If you only sell ONE-TIME products at this time, then the Login Xpress flow below is all you will need to setup as far DAP & 1SC integration is concerned.

If you are selling RECURRING products via 1SC , but DO NOT WANT your users to be automatically logged in to the “Members’ Area” right after their purchase, and you prefer sending them their membership login info (email & password) via email, then you DO NOT need to read this post any further – simply head over to this post: 1ShoppingCart Recurring Payment Processing via Email

But if you sell RECURRING products via 1SC and you DO WANT also want your users to be automatically logged in to the “Members’ Area” right after their purchase, then continue reading this post for Login Xpress setup. After setting up Login Xpress, you will also need to set up the email parsing of orders to allow DAP to process RECURRING payment notifications from 1SC as described here.

Login Xpress Setup

1) Set up your sales page as you would normally do when accepting payment through 1ShoppingCart. The only thing you need to make sure is to use the exact same “Product Name’ in your cart as well as within DAP.

So, if you set up a product called “My Membership Site” within DAP, then use the same name “My Membership Site” as your 1SC  product name.

2) Login to your 1ShoppingCart admin account

Go to Products > Manage Products. Edit Product you are setting up.

Go to the “Links” tab of that Product.

Set up the Thank You URL to point to a DAP script on your site, as shown below:

http://YourSite.com/dap/dap-1shopcart.php?cartId=SecretKey

Note: YourSite.com should be replaced by the name of your site

SecretKey should be set to the same value that you set in  DAP Dashboard > Setup > Config > Payment Processing > Secret Authorization Key used when interfacing with external systems.

The secret authorization key / secret key can be set to anything. They just have to match [in both locations - DAP and 1SC].
Say you set Secret Authorization Key to COOLBEANS. Just make sure SecretKey is also set to COOLBEANS.

For ex - http://YourSite.com/dap/dap-1shopcart.php?cartId=COOLBEANS

DAP Secret Key Setup

3) Now open a brand new browser session where you are not logged in as DAP admin.  Complete a test purchase using an user email that is not already in your DAP.  If the integration worked correctly, then a new user account will automatically get created in DAP, and the user will also be automatically logged in to DAP.  After auto-login, DAP will redirect the users to whatever you configured in DAP under :

DAP Dashboard > Setup > Config > Advanced > URL to which the user is redirected to upon login.

[1ShoppingCart Bonus: Click here to find out how you can get DAP for free ]

DAP does have a built-in shopping cart that allows you to sell both digital & physical products, that will let you replace your 1SiteAutomation.com (private label of 1shoppingcart)  account for the most part. And you can also do 1-click Upsells if you’re using Authorize.net or Paypal Payments Pro.

But DAP’s cart is primarily meant for digital products – like membership and subscription-based products, information products, digital downloads, etc.

It does not have “real-world” physical product features – like “size”, “color”, “quantity”, “sales tax”, “vat”, “volume discounts”, etc.

So, for physical products that require special “physical” features, you’re better off using 1SiteAutomation.com (private label of 1shoppingcart).

And for subscription-based membership and digital products and one-off digital products (products that you sell just once), the DAP cart will more than serve your purpose.

1ShoppingCart BONUS

Click here to find out how you can get DAP for free (for a limited time only).

Starting with DAP v3.9, DAP now has support for ClickBank’s Instant Notification Services (INS).

This is very similar to Paypal’s Instant Payment Notification (IPN).

The ClickBank INS notification will be processed instantly in real time, and your members will receive their welcome email with their membership login info instantly after purchase.

For high-level ClickBank user-flow, see this post.

CB INS Setup

1. Login to your ClickBank account

2. Go to the “Account Settings” tab at the top

3. Click on “My Site” from the sub-menu at the top.

4. Under Advanced Tools, update the Instant Notification Service URL (accept the terms of service etc), and make sure the URL points to:

http://YourSite.com/dap/dap-clickbank.php

Replace YourSite.com above with your actual domain name.

5.  Screenshot below shows Version 1.0, but starting DAP v4.2, we have added support for CB INS 2.1.

So if you’re using DAP v4.2 or later, then select INS Version 2.0 and set the CB INS URL TO :

http://YourSite.com/dap/dap-clickbank-2.1.php

But if you’re using DAP v4.1 or earlier, then select Version 1.0

and set INS URL TO:

http://YourSite.com/dap/dap-clickbank.php

6. Whatever value you put in the Secret Key field in ClickBank (see image above), put the same value (must be ALL UPPERCASE) in to your DAP Admin Dashboard on your web site, at:

Setup > Config > Payment Processing > Secret Authorization Key used when interfacing with external systems

7. The Product Title in CB must match the Product Name in DAP.

8. The Thank You Page url in CB product settings page, should be set to point a static thank-you page you create in your WordPress blog – something like http://YourSite.com/thank-you/ .

And the page should state something to the effect of…

Thank you for your purchase. The download information for the product you just purchased has been sent to the email id you just use during the purchase.

Please check that email id in a few minutes, and you will see an email from us with your login information.

That’s it!

Testing

Make a test purchase.

If the integration was setup correctly, the user will be registered in DAP.  You will find the user account in the DAP Users > Manage screen and you will find the completed transaction / order details on the DAP Orders page.

If the test order is listed in DAP Orders page, then CB is correctly integrated with DAP.  Check the payment status in DAP Orders page. If it says Success, but no welcome/thank-you email got sent, then make sure you set the thank-you email for that product in DAP products page.

Troubleshooting

If no order is listed in DAP orders page for the test purchase, then CB is not integrated with DAP.

To troubleshoot, do the following:

1. Set DAP Setup > Config > Log Level to 5.
2. Empty log content under System -> Logs.
3. Run another test purchase.
4. Send us the log snippet from System -> Logs.

We keep getting requests from folks wanting to switch their existing membership site from WishList to DAP. In some cases, they want to switch their main “bread-and-butter” membership site over to DAP, because of many things that DAP does that the others don’t.

We have finally decided to write a blog post about how to do that for those of you considering it.

[NOTE] You don’t have to do this yourself – we can do the migration for you for a fee. See this link for details about purchasing our WishList-To-DAP Migration Kit. [/NOTE]

1) Migrating “Free Members”

Moving free members over to DAP is very simple. Export your old members as a CSV (comma-separated) file containing just email, first name and last name(optional) in the following order:

Email,FirstName,LastName

Lastname is optional. No spaces before or after the comma’s.

And then import them on the “Users > Add” screen.

You can read more about importing users into DAP in this post.

2) Migrating “Paying Members” With Current Subscriptions

This is a bit trickier than migrating just free members. You not only have to import existing member information, but you also need to migrate over their existing subscriptions to point to DAP.

How this is done, primarily depends on what payment processor you were already using, and wish to continue to use while making sure all new incoming subscription payments get processed by DAP.

But before you migrate over their existing subscriptions, you have to import all of them first using DAP’s “Users > Add” screen, which allows you to import multiple users into a Product, while also marking them as “Paid”.

Before you do the import, be sure to empty both the “Double Optin” and “Thank-you” email subject and body on the Product page, because you don’t want DAP sending out any double-optin or thank-you emails to the members you are about to import. We can send them a broadcast email at a later point, when we’ve fully set them up correctly in the system.

Then once you’ve imported them all, you can modify each of their records quickly to modify their start and end dates, to sync with wherever they were in your previous WL site.

Then once you have all of their dates set up, all that remains is to integrate DAP with your payment processor, such that both payments from both new members as well existing members, all get processed by DAP, so that DAP continue to manage their subscriptions, and start giving them access to the member’s area, going forward.

Paypal Integration

Your current WishList subscriptions are probably already pointing to a WishList specific “virtual” URL. Unfortunately, Paypal will not allow you to modify the IPN url in existing “stored” subscriptions that are current.

So you will need to put in a new rule into your .htaccess file at the root of your web site, to simply redirect all incoming IPN notifications (that come to your WL virtual URL) to DAP’s Paypal-specific file on your site, which is:

http://YourSite.com/dap/dap-paypal.php

Once this is done, DAP will start processing all future subscription payments from existing members.

3) IMPORTANT

Before you create any DAP Products and start protecting content within DAP, make sure you have disabled the Wishlist plugin. Also be sure to disable any other “content protection” plugins, like “Maintenance Mode”.

1) I got an e-mail with this subject:
[DAP] http://yoursite.com: dap-paypal: Invalid IPN Coming In

This can happen if you click on this URL in a browser.

http://yoursite.com/dap/dap-paypal.php (replace yoursite.com with the name of your site).

This is a backend script and should not be called directly via browser. But if you click on this accidently, this error can be ignored.  Just make sure that the DAP and Paypal are integrated and purchases via Paypal are getting registered in dap correctly.

2) DAP Paypal IPN Error (Rejected): IPN Product Name = does not match any DAP Product Name.
But REJECTING MISMATCH it because of your Config settings (Product Mismatch)

Make sure that the item_name in Paypal button is set to eXactly match a DAP product name otherwise DAP cannot process the payment notifications. If the notification is for a product that you sell outside of DAP, then DAP will reject it with this error message and no action is needed.

If you want DAP to process Paypal notifications even if the product name in DAP does not match the Paypal item_name, then enable this setting in DAP :

DAP Setup -> Config -> Payment Processing -> Should DAP process Customer Emails even when the Product names don`t match ->
Set this to “Y” if you want DAP to process non-dap defined product purchase notification from Paypal.

3) Paypal failing with “Check Product and Price(Reprocessible)” in DAP Orders page

Note: DAP Orders page moved under Payment/Coupons menu in DAP 4.0

This could be due to a problem with the CURL library on your site.
With DAP 4.0, you can easily switch your site to use FOPEN instead of CURL.

DAP Setup -> Config -> Payment Processing -> How DAP connects to Paypal -> Select FOPEN

4) Can I use my Paypal account to sell products outside of DAP even if the global IPN points to a DAP script?

Sure. Paypal has 2 IPN settings:

a) Local button level IPN
This one needs to point to the DAP script (http://yoursite.com/dap/dap-paypal.php) on your site so for all sales via this button,
Paypal can send a notification to DAP.

b) Global IPN – under your Paypal profile -> instant payment notification preferences
This one is used by Paypal ONLY if button level IPN is not set. If the button level IPN is set, then Paypal ignores the global IPN.

We recommend that you set both button level and global IPN to point to the same dap script -

http://yoursite.com/dap/dap-paypal.php

(NOTE: replace yoursite.com with the name of your site)

Now, if you are selling other products outside of DAP using Paypal and for those Paypal buttons, if there is no button level IPN notification defined, then Paypal will look at the global IPN setting (which also points to dap) and send notifications to dap. But dap will reject that message because the product is not defined in DAP.
That is when you receive these ‘IPN rejected’ messages and you can ignore them.

5) I have integrated DAP and Paypal per your documentation but it still does not work.

Three key things to watch out for when you integrate DAP and Paypal are:
a) Make sure that the Paypal button has the item_name set to exactly match a DAP product name  otherwise DAP cannot process the payment notifications.

b) Button-level IPN must point to DAP script (http://yoursite.com/dap/dap-paypal.php – replace yoursite.com with the name of your site).

In Paypal button creation page, under “Step 3: Customize advanced features (optional)” tab, within the “Advanced Variables” text box,
enter the following (change the text yoursite.com below to your domain name).

notify_url=http://yoursite.com/dap/dap-paypal.php
Note: replace yoursite.com with the name of your site

c) Global IPN must be enabled and pointed to the DAP script as descrbed in step 1 of this document.

http://www.digitalaccesspass.com/doc/setting-up-your-paypal-button-and-paypal-IPN/

6) What config items in DAP are required if I use Paypal HOSTED button?

If you want to use sandbox for testing, then
DAP Setup -> Config -> Payment Processing -> Use Paypal Sanbox For Testing -> Set to “Y”.

If your site has trouble connecting to Paypal via CURL and you see this error in DAP orders page – Check Product and Price(Reprocessible), then update the config to use FOPEN.

DAP Setup -> Config -> Payment Processing -> How DAP connects to Paypal -> Set to “Y”.

NOTE: In the DAP Products page, you ONLY need to set the Product Price, Trial Amount and Recurring Count if you use the DAP hosted/generated buttons for Paypal.  Not needed if you use Paypal hosted buttons. You can leave it empty if you use Paypal hosted buttons.  Even if you populate it, it will not be used.

If you use the Paypal hosted buttons, then you DO NOT need to set the following in DAP Setup -> Config -> Payment Processing ->

Paypal API Username - Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Password - Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Signature – Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Endpoint - Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.

Paypal Business Email ID - Only needed if you use the DAP generated button for Paypal (DAP Payments/Coupons -> Generate paypal button)

Merchant’s Payment Gateway API Login ID - Only needed if you use e-junkie or the DAP upsell tree plugin for Authorize.net
Merchant’s Payment Gateway Transaction Key – Only needed if you use e-junkie or the DAP upsell tree plugin for Authorize.net
==========================================================

Please check all of the steps at the link below…
http://www.digitalaccesspass.com/doc/setting-up-your-paypal-button-and-paypal-ipn/

Especially check the “notify_url” part towards the end.

If you are absolutely sure that you have followed all of the steps above, and DAP is still not creating an account for the new user, it is possible that your host is not allowing your server and Paypal to communicate correctly. You can confirm if this is an issue, by going to the “Orders” page, searching for all orders, and see if your test purchase in question has been recorded by DAP (even if DAP didn’t give access to the user).

If you find the order in DAP, but the user has not been created, then check with your host and make sure “fopen” or “curl” is enabled for your web site.

If they say it is enabled, and it still doesn’t work, please do the following:

1) Go to Setup > Config > Dap Log Level and set it to “5″.

2) Completely delete test user from DAP

3) Repeat test purchase

3) Go to System > Logs and copy/paste the information there into a support ticket

4) And then please update the ticket with…

* Domain name where DAP is installed
* FTP info
* DAP admin info

And we’ll investigate this asap.

5) Go to Setup > Config > Dap Log Level and set it back to “1″.