|
|
|
 
CPNI adds the ability for you to receive real time
notifications during the payment process. It also adds a higher level
of security for your commerce operations.
The notification process rides on top of the CPI process
so the only real differences happen at the time the transaction is processed
and then how transactions are confirmed. The additions to the transaction
process work like this:

Step one -
What the merchant does: |
| Once the user confirms their order, that order is
sent to CNWB for payment processing. |
What CNWB does: |
| CNWB will post a notification to your server
at a URL that you have specified (You set this up on the website
merchant website). All of your customer's payment information,
any pass through variables, and a piece of encrypted code will be
included in this notification. |

Step two -
What the merchant does: |
| You will receive the notification from CNWB.
You can now do whatever you need to do with that information, like
store it in a database or verify pricing information for the good
or services that are being purchased. The information will include:
customer's payment information, an encrypted code piece, and
any "pass through" variables you may have sent in the
original transaction. Note: Sample code can be provided to you on
request in the form of Coldfusion, ASP, JSP or PHP. |
What CNWB does: |
| CNWB will be looking for a server response ("200")
to make sure you in fact received the information. |

Step three -
What the merchant does: |
| To verify that information submitted by the customer
was indeed valid, you must post all of the form variables you received
exactly as you received them back to CNWB. Your post should
be sent to: https://www.cnwb.com/servlet/CPNI
Note: Sample code can be provided to you on request in the form
of Coldfusion, ASP, JSP or PHP. |
What CNWB does: |
| You will then be waiting for a server response
to your post. The entire body of the response will be a single text
string. You will either get back "VERIFIED" or "INVALID".
When you receive a "VERIFIED" response perform these checks.
1. Check that the "paymentStatus" is "OK"
2. If the "paymentStatus" is "OK", check the
"orderID" against the previous CNWB orders you
have processed to ensure it is not a duplicate.
3. After you have checked the "paymentStatus" and "orderID",
make sure the "merchantSiteID" is the Site ID assigned
to you when you set up your website with CNWB.
4. Once you have completed the above checks, you may update your
database based on the information provided
|
Any "INVALID" responses should be treated with great suspicion. |
See Process Flow Chart
|