This is the old, deprecated version of the DAP Shopping Cart add-on. This is still here for archive purposes only, and should only be used with DAP versions 4.4.x or EARLIER.
This plugin replaces ALL files from both the “Paypal Payments Pro” Upsell-Tree plugin as well as the “Authorize.net” Upsell-Tree Plugin
Starting DAP v4.2, we have consolidated both the Authorize.net & Paypal Payments ProUpsell-TreePlugins into one simple set of files, and it has been named the DAP Shopping Cart, which will allow you to both accept one time and recurring payments, as well as do 1-Click Upsells.
This consolidated set of files is named DAPShoppingCart.zip , and is available for download from the members’ area at http://DigitalAccessPass.com/dap/ .
Upgrading from DAP v4.2
If you are upgrading to DAP v4.2 from a previous DAP version, and you’ve been using Authorize.net or Paypal Payments Pro to accept payments, then you must also upgrade to the new DAP Shopping Cart.
So all you need to is…
1) Download the DAPShoppingCart.zip file from the members area
2) Unzip it to your desktop
3) Upload all files inside directly to your main “dap” folder on your site. (do not upload the folder named DAPShoppingCart – upload only the files inside this folder)
How Self-Service-Store (SSS) worked prior to DAP 4.2
In DAP 4.1, the credits could only be redeemed at product level. So if you wanted to allow users to redeem their earned credits/points towards individual videos, posts, pages etc., you had to create separate child product for each piece of content you wanted to sell because in the self-service-store, the users did not have the option to purchase individual content. They had to purchase the entire child product.
Good news is that DAP 4.2 will allow users to redeem credits at individual content level !!!
DAP 4.2 will support content-on-demand. Users DO NOT have to purchase the entire child product. They can redeem credits towards individual content (that are part of a child product), and pick their own content release schedule rather than a SET drip schedule. So week 1, they can redeem credits toward video 1 and week 2, they can redeem credits towards video 3 skipping video 2. Or they can redeem credits towards both video 1 and video 3 on week 1. They can control how the content is released.
DAP 4.1 flow
1) Say you have 2 master products – Master Product A (10 credits) and Master Product B (20 credits).
2) Say you added video 1/ video 2 / post 1 / post 2 under the child product C. Say that you assigned 5 credits to Child Product C. So to purchase Child product C, the user will have to spend 5 credits.
Make sure you added / associated the child product C to master product A.
3) Say you added video 3/ video 4 / post 3 / post 4 under a child product D. Say that you assigned 12 credits to Child Product D. So to purchase Child product D, the user will have to spend 12 credits.
Make sure you added / associated the child product D to master product B.
4) User 1 purchases Master Product A. The user will get 10 credits.
5) User 1 purchases Master Product B. The user will get 20 credits.
NOTE: The total credits are at master level and the credits earned towards a master can only be redeemed towards child products that are associated to that master.
So when a user buys Master Product A., user will have 10 credits that the user can use towards any child products that are associated to the Master Product A.
When a user buys Master Product B, user will have 20 credits (you can check by clicking on ‘Credits’ in manage users page for that master). The user can use the credits earned by purchase of Master Product B towards any child products that are associated to the Master Product B.
The user cannot use the credits earned from Master Product A towards child products of Master Product B.
You can assign multiple child products to a master. You can assign the same child to multiple masters.
6) User 1 logs in and visits the self-service-store page :
The user will see child product C listed under Master Product A.
The user will see child product D listed under Master Product B.
Now the user can redeem the credits earned from the purchase of Master Product A (10 credits) to purchase the child product C (5 credits). The user can redeem the credits earned from the purchase of Master Product B (20 credits) to purchase the child product D (12 credits).
THE USERS CANNOT PURCHASE INDIVIDUAL CONTENT IN DAP 4.1. THEY HAVE TO PURCHASE THE ENTIRE CHILD PRODUCT.
DAP 4.2 flow
1) Say you have 2 master products – Master Product A (10 credits) and Master Product B (20 credits).
2) In DAP 4.2, you can decide whether you want credits to be redeemed at content level for your store (In DAP admin => Self-Service-Store => Select your child product => Allow credits to be redeemed at content level). By default the users can only redeem credit towards the entire child product. But you can configure the child products to allow credits to be redeemed at content level.
If you decide to allow credits to be redeemed at content level for 1 child, then do the same for all child products to keep the look&feel of your store consistent. Otherwise the store will look messy.
3) Say you allow credits to be redeemed at content level in your store.
In this case you will have to assign content level credits in the DAP admin => Self-Service-Store page ( Self Service Content: “ContentResponder” area).
DAP automatically protects content that you add in the content responder area.
You CANNOT have the same product participate in both self-service-store as well as participate in dripping in dap products page. If you want to have the same child product participate in both self service store and the regular content dripping outside of store, then create a copy/clone of the child product (in dap products page) and give it a different name.
Make sure you added / associated the child product C to master product A.
Make sure you added / associated the child product D to master product B.
4) Say you added video 1/ video 2 / post 1 / post 2 under the child product C. Say that you assigned 1 credit to each content. So to purchase the entire Child product C, the user will have to spend 4 credits (video 1 + video 2 + post 1 + post 2).
OR the user can purchase individual content for 1 credit each.
3) Say you added video 3/ video 4 / post 3 / post 4 under a child product D. Say that you assigned 2 credits to the videos (video 3 & 4) and 4 credits to the posts (post 3 & 4). So to purchase Child product D, the user will have to spend 2+ 2+ 4+ 4 = 12 credits.
4) User 1 purchases Master Product A. The user will get 10 credits.
5) User 1 purchases Master Product B. The user will get 20 credits.
NOTE: The total credits are at master level and the credits earned towards a master can only be redeemed towards child products that are associated to that master.
So when a user buys Master Product A., user will have 10 credits that the user can use towards any child products or contents under the child products that are associated to the Master Product A.
When a user buys Master Product B, user will have 20 credits (you can check by clicking on ‘Credits’ in manage users page for that master). The user can use the credits earned by purchase of Master Product B towards any child products or contents under the child products that are associated to the Master Product B.
The user CANNOT use the credits earned from Master Product A towards child products of Master Product B.
You CAN assign multiple child products to a master. You CAN assign the same child to multiple masters.
6) User 1 logs in and visits the self-service-store page :
The user will see child product C listed under Master Product A. User will see the individual content listed under child product C and they can purchase individual content or the entire child product.
The user will see child product C listed under Master Product B. User will see the individual content listed under child product D and they can purchase individual content or the entire child product.
Now the user can redeem the credits earned from the purchase of Master Product A (10 credits) to purchase the child product C (4 credits) or purchase individual content under child product C (video 1/ video 2 / post 1 / post 2). The user can redeem the credits earned from the purchase of Master Product B (20 credits) to purchase the child product D (12 credits) or purchase individual content under child product C (video 3/ video 4 / post 3 / post 4).
Here’s how you test emails in the system before making them live.
Testing Autoresponder Emails
Create a test DAP Product called “Test Product”
Set up the email drip for this product
Give yourself (or a new test user, but with a real email id that belongs to you) access to this DAP Product on the Users > Manage page (for existing users) or Users > Add page for new users
Run the hourly-cron manually, by going to http://YourSite.com/dap/dap-cron.php . That should send out the day 1 drip for that test user.
Go to Users > Manage page, and back-date the Access Start Date for this test user for the test product, back by one day. So DAP now thinks he bought the product “Yesterday”.
Now run the cron manually again. This time, DAP will send out the day #2 drip for this user.
So every time, move the user’s access start date back by as many days as you want, to trigger that day’s autoresponder email. And each time run the cron manually.
Testing Broadcast Emails
Create a test DAP Product called “Test Product” (or if you have previously created one above, then use the same one)
Add 3-4 test users to this product
On the Emails > Broadcast page, schedule a broadcast email to be sent to “All Users of Product <<Test Product>>”
Run the hourly-cron manually, by going to http://YourSite.com/dap/dap-cron.php . That should send out the broadcast to that test product.
Log in to the email id’s of all the test users that you added to this product, and make sure the email arrived in the inbox.
Selling through Authorize.net, and doing 1-Click Upsells, Downsells and One-Time Offers (OTO’s) are all now extremely simple to implement using the DAP shopping cart plugin, included for free with your purchase of DAP. This post explains how to create buy buttons for selling through Authorize.net.
If you are selling through Authorize.net. DAP itself will act as your shopping cart, and buyers can checkout and make purchases by staying right on your web site. Your site visitors never have to leave your site in order to make a purchase.
Starting DAP v4.2, you can…
1) Customize the shopping cart checkout page (for ex – turn off or on the collection of shipping info in the checkout page, display terms & conditions etc).
2) Get the checkout page to display right within a WordPress page, so the same look & feel as your WP theme is retained on the checkout page.
What you need before you can use this plugin
You need a Authorize.net merchant account
If you want to sell subscription-based products, then you also need Automated Recurring Billing (ARB) enabled in your Authorize.net account.
You must have SSL (secure server) enabled on your web site. Ask your web host to enable SSL for your site.
Unzip it to your desktop. It will unzip the files to a new folder on your desktop, called “DAPShoppingCart”.
Upload all the files inside, directly to your “dap” folder on your web site. DO NOT upload the folder itself.
After the files are uploaded, check to make sure that you find the files checkout.php and checkout-submit.php (just to name 2) directly under the dap folder. If you don’t, then you haven’t uploaded the files to the right directory.
Setup & Config
Log in to your Authorize.net account, then click on “Settings”
Click on the “Silent Post URL”
Set it to http://YourSite.com/dap/dap-silentpost.php . Be sure to change the text “YourSite.com” to your actual domain name.
Back on the the same settings page, click on the “API Login ID and Transaction Key” link towards the bottom, and on the next page, make a note of your API Login ID and Transaction Key on a piece of paper. That page also lets you create a new Transaction key or modify your existing one.
Now log in to your DAP Dashboard and go to Setup >Config > Payment Processing – Authorize.net as shown below.
Enter the API Login ID and Transaction Key that you noted down earlier, into the respective fields, and click “Update”
This step applies to you only if you are already using 1ShoppingCart with DAP (if not, skip to next step): Be sure to remove the “Email Order” cron job from your web hosting control panel IF you have set it up (“Cron Jobs” screen), because you don’t want your orders to be double-processed.
DAP Shopping Cart Customization
In the main DAP Admin menu, go to the “Payment Processing > Cart Options’ page. Here, you can customize the DAP shopping cart checkout page options. The customization needs to be done at a product level (if you want to generate a ‘BUY NOW’ button for your products) AND/OR customize at cart level (select General Settings in the products dropdown on the Cart Optionspage) if you want to generate ADD-TO-CART type of button.
Say that these were your settings for a product called ‘Paid Product 1’.
Show “Coupon Code” N
Show “How did you hear about us?” Y
Show “Comments” Y
Show “Ship-To Address on Checkout” N
Show “Terms And Conditions” Y
Set “Terms And Conditions” – Please accept the terms&conditions by clicking on the checkbox.
Require “User Acceptance of Terms & Conditions” N
Request “Phone” on Checkout? N
Request “Fax” on Checkout? Y
Request “Address2” on Checkout? Y
Here’s how the checkout page will look for the above cart options.
A) Checkout page – BuyNow button – NON-Wordpress version of the Checkout Page
As you can see, shipping info is not there in the checkout page and the ‘howdidyouhearaboutus‘, ‘comments‘, ‘terms&conditions‘ got added to the checkout page based on the settings in the Cart Options page above.
B) Checkout page – BuyNow button – WordPress version of the Checkout Page (on a test site with Mystique theme)
As you can see, the checkout page is now rendered withing a wordpress page. The fields – ‘howdidyouhearaboutus’, ‘comments’, ‘terms&conditions’ got added to the checkout page based on the settings in the Cart Options page above.
Say that these were your settings for ‘General Settings’ in the Cart Options page. These settings will be utilized if you use add-to-cart buttons.
Show “Coupon Code” Y
Show “How did you hear about us?” Y
Show “Comments” N
Show “Ship-To Address on Checkout” N
Show “Terms And Conditions” Y
Set “Terms And Conditions” – Please accept the terms&conditions by clicking on the checkbox.
Require “User Acceptance of Terms & Conditions” Y
Request “Phone” on Checkout? N
Request “Fax” on Checkout? N
Request “Address2” on Checkout? N
A) Checkout CONFIRM page – AddToCART button – NON-Wordpress version of the Checkout CONFIRMATION Page
As you can, the coupon option shows up on the checkout confirmation page as per the CART options above.
The coupon will be applied to each individual item in the cart.
The coupon will only be applied to the products that have been associated to the coupon in the dap admin => add/edit coupons page.
Now when the user clicks on the BuyNow button in the checkout confirmation page then the checkout page will show up like this :
(Checkout page – AddToCART button – NON-Wordpress version of the Checkout Page)
B) Checkout CONFIRM page – AddToCART button – WordPress version of the Checkout CONFIRMATION Page
Generate Authnet Buy Button
14. Now it’s time to generate a customized buynow or add-to-cart button. Go to DAP Payment Processing => Generate Buy Button page and click on the ‘Auth.net & Paypal Pro’ tab.
Here’s how the page looks:
Follow the steps on that page to complete the button generation.
Step 1 (select product & processor)
a) first select the product for which you want to generate the button
b) next select the payment processor (set it to authorize.net if you want to use authorize.net as your payment gateway).
Step 2(generate primary buy button)
a) Now you can generate the button code. First select the button type (addtocart or buynow). Use buynow for subscription products as well as one-time buy products.
b) The Payment Success Page/URL is very critial part of shopping cart flow. DAP uses the URL set in this field to redirect users upon purchase to that page. If you do not want to offer upsells and just want to use basic shopping cart feature without upsells, then just set the URL of your thankyou page in this field. DAP will automatically login the users upon purchase completion to their membership area and then redirect users to whatever you set in the Payment Success Page. If you do want to offer upsells, then set the payment success page to the URL of the first upsell page in the flow.
Ex – http://yoursite.com/thankyou
Ex – http://yoursite.com/myupsellpage
c) Button/Image
If you set the Button/Image to point to the location of buynow or addtocart image, dap will use that image for the button.
Ex – /dap/image/buy.jpg
Ex – /dap/image/addtocart.jpg
If you do not have any image, then leave it blank.
d)
If you want the DAP checkout page (where users enter CC, address etc, to have your WordPress theme look & feel, instead of a basic HTML page’s look & feel, then create a WP page with the merge tag %%DAPCART%% in the page body, save it, and enter the URL of that page here.
Enter the full URL to the page here.
For ex – http://yoursite.com/checkout-page/ (note: this wordpress page just needs to have %%DAPCART%% )
This is how the page will look when it renders in wordpress (button type is ‘BuyNow’)
NOTE: If you leave the field empty, dap will use the non wordpress version of the checkout page.
e) Cart Summary Page in WordPress
Only needed if the button type is “Add To Cart“. Not needed for ‘BuyNow/Subscription‘ button.
If you want the “Add To Cart” Summary Page (where users can see all the cart items, quantity, amount etc) to have your WordPress theme’s look & feel, instead of a basic HTML page’s look & feel, then create a WordPress page with the merge tag %%DAPCARTSUMMARY%% in the page body, save it, and put the URL of that page here.
Enter the full URL to the page in this field.
This is how the page will look when it renders in wordpress for button type = AddtoCart.
You cannot leave this field empty for ‘addtocart’ buttons.
NOTE: If you leave the field empty, dap will use the non wordpress version of the summary page.
f)
Only applicable to button type = “Add To Cart“. Not used for ‘BuyNow/Subscription‘ button. This should contain the URL of the page to which you want to take the users if they add items to cart and then want to ‘go back to shopping’… they are not ready to checkout yet.
You can put the full url of the page where you have other ‘add-to-cart’ buttons so the user can continue shopping.
You cannot leave this field empty for ‘addtocart’ buttons.
=====================================
ALL SET.
Now generate the BuyNow /AddToCart / Subscription button HTML code for your product, which you can then directly paste into your sales page.
Note: The price, trial price, and recurring options are all taken from your Product settings from DAP products page.
authnet_buybutton_code
Generate Authnet Upsell Page Buy Button / No Thanks code
15. If you’re doing upsells, the only thing you need to do is, set the “payment_succ_page” field in button code generated above to the upsell page.
for ex – Payment Succ Page URL = https://yoursite.com/myupsellpage
Now to generate the button code for the upsell page, go to DAP Admin => Payment Processing => Generate Buy Button page. Click on Auth.net & Paypal Pro tab.
Then go to section 3 – Generate “Upsell” / “No-Thanks” Button
a) Choose the right button type –
AddtoOrder (to allow the user to add the upsell item to cart) OR
No Thanks (the upsell item on this upsell page will be ignored, the transaction will be completed with the current cart items).
b)
User is directed after ‘AddToOrder’ or after ‘No, Thanks’ to whatever you set in the Payment Succ Page. If you want to offer more upsells, then set the url of the next upsell page in this field. DAP will first add this order to the cart, then redirect users to the next upsell page. If no more upsells, you can set the url of the thankyou page in this field. DAP will first add this order to the cart, then redirect users to the thankyou page.
For ‘No, Thanks’, you can set the url of the next upsell page in this field or set the URL of final thankyou page in this field. If the URL of next upsell page is set, DAP will just ignore the current product being upsold to the user and redirect user to the next upsell page. If no more upsells, you can set the url of the FINAL thankyou page in this field. DAP will redirect users to the thankyou page.
NOTE:
You can repeat this process for unlimited upsells, downsells and one-time offers. No limits.
Product Price:
For a 1-time purchase product, this is the product’s purchase price. For a recurring product, this is the “recurring” price (what the customer gets charged month after month).
B) Trial Amount: This is only if there’s a trial amount. If no trial, leave this empty.
C) Recurring Count: How long is your subscription? If you said “Forever”, then enter the number 9999 here. If it ends after 6 months, then enter 6 here.
16. Set these fields to valid values.
17. NOTE: The DAP Authorize.net allows 1 trial. So in the recurring cycle fields, make sure “Payment/Trial Period #2” and “Payment/Trial Period #3” are both the same (set to same number of days: like 30). Example below shows the setting for a “7 day” trial period, followed by recurring payments every “30 days”.
authnet_recurring_cycle
18. If you are not offering a trial, then just set the Trial Amount to $0.00. But if you really wanted to offer a FREE TRIAL, then you must set the Trial Amount to at least $0.01 (1 penny).
19. Once you’ve saved the product, you can now click on any of the two new “Generate… Button Code” links that are located right below the product list combo box.
newproductspage2
That’s it. The upsell page can be a wordpress page or a static HTML page.
While it looks like a LOT of steps, that is only because we have to explain the steps in detail so they are clear. In reality, it is very simple to set up, and starting from scratch, if you have DAP & SSL already installed, it shouldn’t take you more than 1/2 hour to set up your 1-Click Upsells/Downsells/OTO’s. And if you’re not using Upsells/Downsells, then it can be done even faster.
If you have any further questions, feel free to open a support ticket, and we will assist you in getting this going.
Content entered here will appear under the Terms And Conditions on the checkout page.
In DAP 4.2, we have added the support for admin defined custom-fields. You can define your own custom fields in DAP admin panel, accept/store the custom fields via DAP Free Signup/Registration form and it can be viewed/managed in the DAP admin panel.
We have also added the ability to allow the admins to refer to the custom field values via merge tags within DAP email messages (auto-responder/broadcast).
Here’s a screenshot of the DAP admin panel => Users => Custom Fields page.
(Click to enlarge)
Here’s the steps to define your own ‘custom’ field in DAP admin panel => Users => Custom Fields page.
Step 1: Database Field Name
Define the fieldname. DAP will use the name defined here to manage this field. The database field name is also used within the dap direct signup form/html so when the user’s enter a value for the field during sign-up, DAP will store it in the right database field.
If you want to accept any custom field via the DAP direct signup form, then use the database field name defined here as the field name in the direct signup HTML code generated from DAP products page.
Ex –
The Label will appear on the user’s profile page. The database field name is only for internal use… the label is what the user’s will see.
Screenshot of user profile page with sample custom fields – Social Security and Tax ID.
Here the label names are Social Security and Tax ID.
(Click to enlarge)
Step 3: Description
Just for Admin User to describe the custom fields. Not displayed to the user.
Step 4: Show Field Only To Admin
NOTE: If you want the users to see and update the custom field, set ‘Show Field Only To Admin’ to ‘N’.
If this is set to “Y”, then only admin will see this field in the DAP admin -> manage users page (when you click on the user’s name).
2) Using Custom Fields in Signup Form
Say you want to include a field called “Tax Id” in your Free Signup Form that you generated in DAP Products page.
So first define a custom field with the database field name tax_id in the Custom Fields page in DAP Admin (as shown above).
Here’s the default free signup form code generated from dap products page (if your form code looks different, see the last section at the end of this post).
So basically, you add the word ‘custom_‘ in front of the custom field’s database field name. So if the database field name is “tax_id“, then in the form, it becomes custom_tax_id (as you see above)
So your final free signup form will look like this:
Put the signup form code on your WP page/post/sidebar, and the form is displayed like this…
You can do the same for each custom field you want to accept in the dap free signup form:
1) Create the custom field in DAP Admin -> Users -> Custom Fields Page
2) Add the field to the free signup form as shown in the example above for tax_id.
Displaying Custom Fields On Your Site
You can display the value of the user’s own custom fields on your pages, using the merge tag like this:
%%DAPCUSTOMFIELD_tax_id%%
Using Custom Fields In DAP Emails
You can send custom field values in the DAP emails by using merge tags like this – %%custom_tax_id%%
Add ‘custom_’ in front of the custom field’s database field name.
So if you have defined a custom field called tax_id in your database, to include this field in the autoresponder/broadcast email, just add this – %%custom_tax_id%% to the body of your email.
That’s it. When the user receives the email, dap will automatically replace the merge tag with the user’s tax id value.
So if your email message body contains the following text:
Your Tax Id: %%custom_tax_id%%
When the user receives the message, it will look like this (in this example, the user’s taxId = 9999):
Your Tax Id: 9999
If you are using an older version of DAP < 4.4.3, then see the section below.
When you have hundreds of posts or pages protected as part of a DAP Product, the list of links on the DAP Member Home Page (that is the result of using the merge tag %%USERLINKS%%) can get quite long and unwieldy.
So you can choose to hide some of those links from being displayed on the member’s home page.
Here’s how you hide a link from being shown on the member’s home page…
1) Go to the DAP Product in question, scroll down to the ContentResponder section
2) Click on the edit link next to the content in question on the right. The “Edit Files” popup will then show up on the left.
3) Set “Display On User’s Home Page” to “N”.
That’s it.
The content is still part of that product, it is still being protected, but the link simply won’t be displayed on the member home page.
He stays a member for about 3 months. Let’s say it’s now mid March. He wants to take a couple of months break. So he goes on a 2 month break. Comes back end of May and wants to resume his membership.
DAP allows him to pick up right where he left off – which is continuing to receive content as of April (04/01/2011), even though today’s date is May 25th, 2011.
So while he took a break, other members who did not take a break in membership, continued to pay for those 2 months, and continued to receive content dripped through those months. So it is only fair that when he does come back end of May and resumes his subscription, he does not resume from June’s content, but from April’s content (when he last put his membership on “Pause”).
It’s ok if you’re not dripping content on a monthly-basis, but rather on a “day” basis. So to put it in terms of “days”, when Joe resumes his subscription, since he was already 90 days old in the system when he put his subscription “On Hold”, and comes back another 60 days later (roughly about 2 months), then DAP will start dripping Day #91 content onwards for him, and NOT Day #151 onwards (he didn’t pay for 2 months in between).
This is how DAP works right out of the box. Nothing special to configure. And DAP automatically takes care of pausing the dripping when he is not paying.
WARNING: Just remember that in order for you to put his actual payments on hold, you will need to have a payment gateway like Authorize.net or Paypal Website Payments Pro. Or you must be using a shopping cart like http://1SiteAutomation.com . Using something like Paypal Standard or ClickBank will not allow you to put the actual charging of his credit card on hold.
NOTE: If you actually did want him to start receiving current content even though he left for 2 months, then all you have to do is, once he comes back and starts paying again, just extend his access end date on his account (which will initially be showing 03/31/2011 – end of March, when he left) and modify it and make it 05/31/2011. So when his next payment comes in after he resumes, DAP will extend his access end date to 06/30/2011 – which means, he can now access all of the current content.
There is no pre-registration in dap. Upon completion of purchase, the user is automatically logged-in to their membership area. You can also choose to redirect users wherever you want (button level redirect) upon purchase.
Here’s how user flow works.
http://www.digitalaccesspass.com/doc/user-flow/
Paypal Hosted Button (Paypal Standard)
Buy Now / Subscription / AddToCart
* Buyer clicks on the button (button created within your paypal account) on your sales page
* Buyer is taken to the Paypal page.
* Buyer completes the payment successfully
* Buyer is transferred back to whatever you set in the button-level return url within Paypal.
* In the meantime, Paypal notifies DAP via IPN about the purchase. Make sure you integrated DAP and Paypal hosted button using this document.
* DAP automatically creates the member account, and sends thankyou email (configured in your dap products page) with login info to the buyer. Make sure to setup the thankyou email in the DAP products page for all the products you sell via DAP.
* When the users login to their membership area, they will be redirected to either product-level logged-in URL or global logged-in url based on whether they have access to just 1 product or multiple products. The product level logged-in url is used if the user has access to just 1 product. The global logged-in url (under dap setup -> config -> advanced -> url to which user is redirected upon login) is used when user has access to multiple products.
* Note: You can create a members area and redirect users to that page upon purchase.
DAP Generated Paypal Button (Paypal Standard)
Buy Now / Subscription / AddToCart
* Buyer clicks on the button (button created within DAP Payment/Coupons -> Generate Paypal Button) on your sales page
* Buyer is taken to the Paypal page.
* Buyer completes the payment successfully
* Buyer is transferred back to your site where dap does all of the following :
– automatically creates the member account
– automatically logs-in the user to their membership area
– automatically redirects the user back to whatever you set in the redirect tag in the button code.
Note: If you do not set redirect tag in the button, then dap will automatically redirect users to product-level or global-logged-in URL based on whether they have access to just 1 product or multiple products. The product level logged-in url is used if the user has access to just 1 product. The global logged-in url (under dap setup -> config -> advanced -> url to which user is redirected upon login) is used when user has access to multiple products.
* Make sure you integrated DAP and Paypal hosted button using this document.
* DAP also sends thankyou email (configured in your dap products page) with login info to the buyer. Make sure to setup the thankyou email in the DAP products page for all the products you sell via DAP.
* Note: You can create a members area and redirect users to that page upon purchase.
Clickbank
* Buyer clicks on the button (button created within your clickbank account) on your sales page
* Buyer is taken to the Clickbank page where they can complete payment
* Buyer completes the payment successfully
* Buyer is transferred back to whatever you set in the thankyou URL in CB for the product.
* In the meantime, Clickbank notifies DAP via INS (instant notification service) about the purchase. Make sure you integrated DAP and Clickbank using this document.
* DAP automatically creates the member account, and sends thankyou email (configured in your dap products page) with login info to the buyer. Make sure to setup the thankyou email in the DAP products page for all the products you sell via DAP.
* When the users login to their membership area, they will be redirected to either product-level logged-in URL or global logged-in url based on whether they have access to just 1 product or multiple products. The product level logged-in url is used if the user has access to just 1 product. The global logged-in url (under dap setup -> config -> advanced -> url to which user is redirected upon login) is used when user has access to multiple products.
* Note: You can create a members area and redirect users to that page upon purchase.
Buyer->Affiliate Association
You need to connect your payment processor to DAP first so buyer’s purchase is registered in dap. If your payment processor is not connected to dap, there is no way for dap to connect the affiliate and the buyer.
1) It starts with the prospect/buyer clicking on the affiliate link. When prospect/visitor clicks on the affiliate link, a cookie gets set on their computer.
2) The buyer completes the purchase.
3) You should now see the buyer’s account in DAP admin -> Users ->Manage page. NOTE: you must integrate the payment processor with dap so the buyer will be automatically registered in dap upon successful purchase as described in the Userflow – DAP Generated Paypal Button above.
4) Then the user logs in to the membership area after purchase. When the user logs in, dap checks if an affiliate cookie exists, and if it does, it creates an association between the buyer and the affiliate in the database. This association occurs during login.
NOTE: If you use dap generated button for Paypal or the DAP shopping cart, DAP automatically logs in the user to their membership area upon purchase. So the association between buyer and affiliate is automatic right after purchase. But if you use a payment button where the user is not auto-logged in upon purchase, then the user/buyer must login to their membership area in dap atleast once for the association between buyer-> affiliate to occur.
5) When the DAP cron runs at the top of the hour, then the affiliate gets credited. Until then, you will see an association between the user->affiliate in the DAP -> Users ->Manage page but the sales commission wont be reported. After the cron runs, the affiliate is awarded commission.
To test this: you can manually run the cron in a browser (http://yoursite.com/dap/dap-cron.php – replace yoursite.com with the name of your site).
We do not recommend that you run the cron manually because it can time out (if there are too many items to be processed). So you should wait for the automatic cron run at the top of the hour. But if the commission does not occur at all, then run it manually. If the manual run works ok, then it means that your automated cron setup is not working. Check the CRON setup in your webhost control panel -> Cron tab. See if the DAP hourly cron (dap-cron.php) is setup to run once every hour.
If not, it needs to be setup as described here: http://www.digitalaccesspass.com/doc/setting-up-cron-jobs/
Please note that an affiliate will get their commissions credited only if there’s an actual payment (transaction) in the system for that purchase.
So if you have marked someone as “PAID”, for whatever reason, then even if there is an affiliate associated with that user, then the affiliate is not going to get credited any actual commissions because there is no payment in the system.
Here’s how to manually credit affiliates for a sign-up or purchase…
1) Add Transaction If None Exists
If there is no payment associated with the purchase, and you’ve marked the user as “FREE” or “PAID”, then you must first enter an order (transaction) into the system. So search for the user by email id on the Users > Manage page, and on their row for that Product, click on “Add Trans” (which stands for “Add Transaction”).
2) Add Transaction Amount – If None Exists
When you click on the “Add Trans” link, you will see a small popup appear (see image below) that allows you to manually enter an order. So if the purchase was for say $97, then you would enter “97” or “97.00” in the “Order Amount” field and click on “Submit”.
3) Verifying Order Id
Once you’ve entered a manual order, the “Trans Id” column will change from “PAID” to an actual transaction (or order) id – in the example below, it turns to Transaction Id “3”.
4) Give Manual Credit To Affiliate
Now that there’s an order in the system, it’s time to manually give credit to the affiliate. Now on the same User row, scroll all the way to the end, and under the “Aff Id” column, if you already see a number, then it means some other affiliate is already associated with this purchase. You cannot change that affiliate id at this time.
But if you see a “+” (plus sign) there instead of a number, it means that no affiliate is associated with that purchase yet, and you will be able to give credit for that purchase or sign up to any affiliate in the system.
So when you click on the “+” sign, you will see a small popup come up, which allows you to enter the affiliate id (must be a number) of any user in the system. Please note that ever user has a unique number (“User Id”) associated with their account. That’s the number you should enter here.
5) Verifying Manual Credit
Let’s say you gave credit to Affiliate Id 5 for this purchase. So now you should see the “+” sign at the end of the row change to “5”. That means, user #5 has been given affiliate credit for this purchase. So assuming you have already set up affiliate commissions for this product (under Affiliates > Set Commissions ), then at the top of the next hour, when the hourly cron job runs, the affiliate commission will be “credited” the affiliate’s account depending on the commissions set up for the product.
WARNING
Sometimes you may enter a manual transaction for a purchase at the same time DAP is processing an automated transaction for that same purchase.
That means, there are now two transactions in DAP for the same purchase – which can cause problems in accounting.
At the very least, you may end up paying double commissions to the affiliate who referred the user, because all affiliate commissions are calculated from sales, and if you have two entries for the same purchase, then the affiliate will get paid twice.
So if you see two credits for the affiliate, you must note that it will not be for the same transaction, but for different transactions.
So be careful when you’re entering Manual transactions. That is only for when there is no way to automate it in DAP, and you’re unable to bring the transaction into DAP automatically.
If you see two affiliate commission credits (one for the automated transaction that DAP picked up, and one for the Manual transaction that you entered), then just refund the manual transaction in DAP. There will probably be a change to the user’s access because of the refund. So make a note of the current access of the user BEFORE you do the refund, and then AFTER you’ve processed the refund, go back to the User’s details on the Users > Manage page, and manually adjust their access to make sure it’s accurate.
