We're currently running a Black Friday "Buy 1 Get 1 FREE" promo. Click here for details.
Note: This service is intended for use by experienced programmers. Users without extensive programming skills should refrain from implementing the ZPN without first enlisting the services of an experienced programmer.
Zaxaa Payment Notification or ZPN is a notification system that sends payment details and customer's information to your server. You can use the given information for any post-payment operations, such as:
When you turn on the ZPN feature, Zaxaa notifies you as soon as a transaction has been made successfully and posts all the payment details to a URL specifies by you (ZPN Listener).
ZPN Listener is the script that you host on your own server that will process and handle the payment notification message sent by Zaxaa. You (or your programmer) can write the script using web programming language(s) or your choice.
Zaxaa can send notifications for these type of transactions:
Let's assume you've already created products and set up the sales funnel in your Zaxaa account, and want to integrate the ZPN with your custom membership script.
Here's how you can enable the ZPN feature:
Note #1: If you enable the multi-price feature (a product has more than one price variant), then there'll be multiple ZPN URL fields too. For example, if someone bought your product for price variant #1, then Zaxaa will send the ZPN notification to ZPN URL #1. If someone bought price variant #2, then Zaxaa will send it to ZPN URL #2. In other words, you will need to enter multiple ZPN URLs when using the multi-price feature. You can enter a different ZPN handler script URL for each price variant or simply enter the same ZPN handler script URL.
Note #2: If you have setup the "OTO" funnel in your front-end product settings, Zaxaa will also send notification each time your customers purchase the OTO. ZPN will be sent to ZPN URL specified on the front end product settings. ZPN for OTO transactions may contain information or variables for multiple products, while ZPN for front-end transactions will ONLY contain information for a single product.
Note #3: When using the multi-price feature, the OTO ZPN will depend on the Front-End's price variant. For example, if the customer bought price variant #2 and then the he/she also bought the OTO, then both ZPN notification for Front-End and OTO will be sent to the frontend's ZPN handler script URL #2.
Note #4: Zaxaa also have the "Evergreen OTO" feature that allows customers to buy the OTO without having to buy the front-end first. If this is the case, ZPN will be sent directly to the ZPN URL that is specified in the OTO product settings.
Another important data that will be needed by your ZPN listener script is your unique API Signature. Your script must use your own API signature to verify the validity of the notifications.
How to obtain your API Signature:
Please see the ZPN sample code to find out how to use your API Signature to prevent fraud.
Once you've enabled ZPN in your Zaxaa account, ZPN will be triggered every time a new transaction is created or an action is taken upon a transaction in your Zaxaa account.
Here's a quick illustration of how this works:
Related Information : Zaxaa Payment Data Transfer (PDT)