If you have products that have a price, you need to define at least one payment method for your site to use or your users will not be able to checkout properly. The only time a user can check out is when their cart has items in it that have no cost.
The left side of the page is a read only grid showing a list of every defined payment processing configured in the site, even those not configured. You can configure which payment options you want the user to be able to pick from during check out in this page.
The grid has columns showing how each payment processor is configured. By default no payment processors are configured for use. The columns show the following information:
-
Def – If checked, the payment processor has defined values for the site in the database.
-
Use – If checked, the payment processor is in use and will be considered for offering to the user during checkout. Depending on the user and options set for the payment processor, a user may not be shown the option.
-
Test – If checked, the payment processor is in its “test mode” and will not actually process the payment so that money is be transferred. Each payment process should have the option to be used in test mode so that you can validate your configuration before going live.
-
Name – The name of the payment processor as defined by it. The default deployment of Syrinx CS comes with a handful of payment processors, but new 3rd payment processors can be written and added to this list.
Payment Processor Details Area
The right side of the page shows the details of the selected payment processor in the grid. Each payment processor will have its own options and directions on how to configure it.
Each payment processor can be configured for what type of users can pick it as an option during checkout. Using the radio buttons shown in the image below, you can control the access.
The default is to allow all users to be able to pick the option during checkout. If you select the radio button to only let certain user groups use the option, a checkbox list of the currently defined user groups appears below it. You can then check as many user groups as you want to have access to this option during checkout.
Approval or denial of the transaction by the payment processor is used to control checkout completion.
Generic CC Collection Processor
This payment processor is used to collect basic credit card information from the user, but doesn’t actually validate the credit card other than basic known lengths and other formatting information as well as the expiration date being in the future.
This is a good payment choice when you just want to collect the information so that you can process it some other way later. An example is when you don’t ship the product and the user has to go to the location of the product to pick it up and pay for it then. In that type of situation, the credit card is used to help affirm the user’s commitment to the purchase. This is especially good in situations where the final price is very likely to change at the last point of pickup and purchase.
PayPal Express Checkout Processor
This allows customers to use their PayPal account to pay for the sale. The user is redirected to the PayPal website where they can pick their funding source, validate the order and even change the shipping address.
You need to provide the PayPal merchant information provided by them including:
-
API Username
-
API Password
-
API Signature
PayPal Credit Card Processor
This allows customers to pay with their credit card directly on the site, without ever navigating to the PayPal site. Customers do not have to have a PayPal account to use this option, just a valid credit card accepted by PayPal.
You need to provide the PayPal merchant information provided by them including:
-
API Username
-
API Password
-
API Signature
Intuit QBMS Payment System Processor
This allows customers to pay with their credit card directly on the site, without ever navigation away from the site during the transaction.
You need to go through a fairly elaborate process to get the Intuit payment processor working, which is due to the way Intuit manages their security. The details area shows two links to the Intuit merchant site to initiate the process. One is for getting a “connection ticket” for production usage, and one is for getting a “connection ticket” for testing usage.
Once you go the the Intuit process, you end up with two pieces of information needed for the processor to work properly on the site.
-
QBMS App ID
-
QBMS Connection Ticket
Authorize.Net Payment System Processor
This allows customers to pay with their credit card directly on the site, without ever navigation away from the site during the transaction.
Authorize.Net is currently one of the most credit card processing systems available. You can easily signup for an account on their site, which you are then given the two pieces of information needed to use the system. You can get a test id without needing to go through the merchant approval process, which is a great way to test your site checkout process before going live.